From owner-freebsd-current  Fri Jan 14  5: 4: 8 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 7D394151C4
	for <current@FreeBSD.ORG>; Fri, 14 Jan 2000 05:04:01 -0800 (PST)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id OAA04565;
	Fri, 14 Jan 2000 14:03:42 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200001141303.OAA04565@freebsd.dk>
Subject: Re: ATAPI CDROM trouble
In-Reply-To: <XFMail.000114232854.darius@dons.net.au> from "Daniel J. O'Connor" at "Jan 14, 2000 11:28:54 pm"
To: darius@dons.net.au (Daniel J. O'Connor)
Date: Fri, 14 Jan 2000 14:03:42 +0100 (CET)
Cc: current@FreeBSD.ORG, vova@express.ru
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Daniel J. O'Connor wrote:
> 
> On 14-Jan-00 Soren Schmidt wrote:
> >  Dont define this until you know the drive is functioning otherwise,
> >  LOTS and I mean LOTS of atapi devices dont do DMA even if advertised.
> 
> Would it be possible to implement this as something like a 'quirk list'?
> 
> ie list known good (or bad) drives and enable (or disable) DMA on them.

It would have to be a list of known good drives on known working chipsets,
in effect a list that would be next to impossible to maintain.

If you have ATAPI hw that are more than 6-12month old, bets are it
wont work, newer devices seems more capable, but still alot of
them claim to support DMA, but fail utterly always or on some chipset
combinations.

The only way to know is to try it out and see for yourself, the ATAPI
device manufactures should have thier fingers smacked, hard ....

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message