From owner-freebsd-current Tue Dec 21 9:11:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EB6DA14D0B for ; Tue, 21 Dec 1999 09:11:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA06606; Tue, 21 Dec 1999 18:11:41 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912211711.SAA06606@freebsd.dk> Subject: Re: Problems with the ATA-driver In-Reply-To: from Doug White at "Dec 21, 1999 08:53:44 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Tue, 21 Dec 1999 18:11:41 +0100 (CET) Cc: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren), freebsd-current@FreeBSD.ORG 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 Doug White wrote: > > > > It probably because I relaxed the requirements for doing WDMA on disks > > that doesn't bother to tell whihc verson of the ATA spec they conform to. > > I think your case is the more seldom one, but I'm this close to > > blacklisting all WD/Maxtor drives, that would make life alot easier... > > If you end up doing this, can you have the driver print a line letting > people know this is intentional? i.e., > > ad0: DMA disabled: This drive does not properly support DMA mode. > ad0: To force DMA for this drive (at your own risk) set flags 0xXX. Sure, but belive me, this is _the_ last thing I want to do, but its starting to look as if its the only possibility... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message