From owner-cvs-src@FreeBSD.ORG  Fri Jul  2 19:30:15 2004
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 86CB216A4D1
	for <cvs-src@FreeBSD.org>; Fri,  2 Jul 2004 19:30:15 +0000 (GMT)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1ACC743D48
	for <cvs-src@FreeBSD.org>; Fri,  2 Jul 2004 19:30:15 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: (qmail 6148 invoked from network); 2 Jul 2004 19:29:18 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 2 Jul 2004 19:29:18 -0000
X-pair-Authenticated: 209.68.2.70
Date: Fri, 2 Jul 2004 14:29:16 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Warner Losh <imp@FreeBSD.org>
In-Reply-To: <200407021342.i62DgamV027295@repoman.freebsd.org>
Message-ID: <20040702142635.F63950@odysseus.silby.com>
References: <200407021342.i62DgamV027295@repoman.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jul 2004 19:30:15 -0000


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?

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.)

Mike "Silby" Silbersack