From owner-freebsd-current Wed Dec 22 4: 5:10 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 9E13814E3B for ; Wed, 22 Dec 1999 04:05:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA43886; Wed, 22 Dec 1999 13:04:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912221204.NAA43886@freebsd.dk> Subject: Re: Problems with the ATA-driver In-Reply-To: from Nick Hibma at "Dec 22, 1999 12:30:08 pm" To: n_hibma@webweaving.org (Nick Hibma) Date: Wed, 22 Dec 1999 13:04:57 +0100 (CET) Cc: dwhite@resnet.uoregon.edu (Doug White), 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 Nick Hibma wrote: > > 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. > > Let's not go the Linux way and make the boot messages slow down booting. Agreed. > Mentioning it in the manpage should be sufficient I guess. Blacklisting > devices sounds like a good idea if tey fail to work correctly in many > cases. The problem being how to get a list that is "good enough" for the majority of cases. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message