From owner-cvs-all@FreeBSD.ORG Fri Jul 2 20:15:53 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 138B716A4CE; Fri, 2 Jul 2004 20:15:53 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFCDE43D49; Fri, 2 Jul 2004 20:15:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i62KBO2V013523; Fri, 2 Jul 2004 14:11:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 02 Jul 2004 14:11:58 -0600 (MDT) Message-Id: <20040702.141158.68038729.imp@bsdimp.com> To: silby@silby.com From: "M. Warner Losh" In-Reply-To: <20040702142635.F63950@odysseus.silby.com> References: <200407021342.i62DgamV027295@repoman.freebsd.org> <20040702142635.F63950@odysseus.silby.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/pci pci.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 20:15:53 -0000 In message: <20040702142635.F63950@odysseus.silby.com> Mike Silbersack writes: : : On Fri, 2 Jul 2004, Warner Losh wrote: : : > imp 2004-07-02 13:42:36 UTC : > : > FreeBSD src repository : > : > Modified files: : > sys/dev/pci pci.c : > Log: : > Disable native ata support for now, too much breaks : : So that the rest of us know what to look for, could you give a little more : detail? Does native ata mode provide any benefits that would be : noticeable over legacy mode? Also, when it breaks, does that just mean : the devices don't probe, or does it mean that data corruption might occur? Native ata mode gives little to no benefit over non-native mode. It allows one to map the device's resource better in terms of overall system resource usage, but that's a minor addition. I don't think that there is any other wins to doing that. Devices either don't probe or don't work. I don't think that you'd see 'working mostly, with some data corruption'. The big win comes in when we have devices that don't run in legacy mode at all... : I ask because I have a CD-ROM that has never worked in DMA mode, and I was : wondering if native mode might fix that. (After jhb fixed my pccard+ACPI : problem by adding better EISA support, I'm optimistic about everything.) I doubt it. Feel free to enable the ifdef and try :-) Warner