From owner-freebsd-current Tue Dec 21 8:53:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id D636C14FF6 for ; Tue, 21 Dec 1999 08:53:49 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA30198; Tue, 21 Dec 1999 08:53:44 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Dec 1999 08:53:44 -0800 (PST) From: Doug White To: Soren Schmidt Cc: Theo van Klaveren , freebsd-current@FreeBSD.ORG Subject: Re: Problems with the ATA-driver In-Reply-To: <199912211448.PAA82306@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Soren Schmidt wrote: > > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and > > Western Digital Caviar (2.5 GB), DMA-33. > > Mainboard: Asus P5A-B Super7 > > Chipset: ALi Aladdin V AGPset > > 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. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message