Date: Mon, 10 Dec 2007 00:12:00 -0500 From: Travis Mikalson <bofh@terranova.net> To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@deepcore.dk>, freebsd-current@freebsd.org Subject: Re: Any successful installs on a Broadcom HT1000 chipset? Message-ID: <475CCAA0.5040900@terranova.net> In-Reply-To: <475CC426.3060808@terranova.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?475CCAA0.5040900>