From owner-freebsd-current@FreeBSD.ORG Mon Dec 10 05:12:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 202B316A417 for ; Mon, 10 Dec 2007 05:12:05 +0000 (UTC) (envelope-from bofh@terranova.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id E949C13C442 for ; Mon, 10 Dec 2007 05:12:04 +0000 (UTC) (envelope-from bofh@terranova.net) Received: from [216.89.228.170] (host-216-89-228-170.wireless.terranova.net [216.89.228.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tog.net (Postfix) with ESMTP id 4020029B61C; Mon, 10 Dec 2007 00:12:04 -0500 (EST) Message-ID: <475CCAA0.5040900@terranova.net> Date: Mon, 10 Dec 2007 00:12:00 -0500 From: Travis Mikalson Organization: TerraNovaNet Internet Services User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= , freebsd-current@freebsd.org References: <73807.10710.qm@web63912.mail.re1.yahoo.com> <200711280842.09340.jhb@freebsd.org> <474D726A.8080807@deepcore.dk> <200711280938.38545.jhb@freebsd.org> <474E5B69.7070406@yandex.ru> <474E65D6.4040403@deepcore.dk> <474E69AE.7000105@yandex.ru> <475978E1.2090507@deepcore.dk> <475C6C3E.6070004@deepcore.dk> <475CC426.3060808@terranova.net> In-Reply-To: <475CC426.3060808@terranova.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Any successful installs on a Broadcom HT1000 chipset? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Dec 2007 05:12:05 -0000 Travis Mikalson wrote: > So this is a successful workaround for the HT1000 on-board SATA, and it > looks like this additional workaround you just posted is pretty > universal and would also limit a Marvell PCI-X SATA controller's DMA size. Er, scratch that, I see the max_iosize you set is in ata_serverworks_allocate() so this fix wouldn't help with a Marvell SATA controller plugged into the HT1000 system's PCI-X slot. I also see this isn't first and only chipset to have the exact same dma max_iosize limit imposed :) -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 x101 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Life's not fair, but the root password helps.