Date: Fri, 02 Jul 2004 10:53:36 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: gallatin@cs.duke.edu Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/dev/pci pci.c Message-ID: <20040702.105336.11626631.imp@bsdimp.com> In-Reply-To: <20040702120442.A8994@grasshopper.cs.duke.edu> References: <xzp4qoqijr1.fsf@dwp.des.no> <40E57442.8000602@deepcore.dk> <20040702120442.A8994@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040702120442.A8994@grasshopper.cs.duke.edu> Andrew Gallatin <gallatin@cs.duke.edu> writes: : S=F8ren Schmidt [sos@deepcore.dk] wrote: : > Dag-Erling Sm=F8rgrav wrote: : > > Warner Losh <imp@FreeBSD.org> writes: : > > = : > >> Log: : > >> Disable native ata support for now, too much breaks : > > = : > > = : > > Could this be controlled by a hint or a tunable? : > = : > We'll soon need something better than that, since systems that need= s = : > this to boot at all will appear in the not too distant future. : > Question is how to deal with old systems where the config is borked= in = : > some sense... : = : Is there any commonality between the broken systems? : Mine is a ServerWorks based system. Details at : http://people.freebsd.org/~gallatin/ata_irq/ : = : At the very least, we could have a quirk table.. ServerWorks seems to be a problem child for the new ata code. It has busted a few times now as changes have gone in. I believe that if the ServerWorks ata is broken, then I have a laptop that is also broken... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040702.105336.11626631.imp>