From owner-cvs-all Thu Mar 22 7:30:48 2001 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 692A137B719; Thu, 22 Mar 2001 07:30:43 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2MFUgh10495; Thu, 22 Mar 2001 10:30:42 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 22 Mar 2001 10:30:42 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Takahashi Yoshihiro , sos@FreeBSD.org Cc: jkh@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc MAKEDEV In-Reply-To: <20010322.192850.125117261.yosihiro@cc.kogakuin.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Mar 2001, Takahashi Yoshihiro wrote: > This breaks pc98 supports. We still uses the wd driver because the ata > driver does not support pc98 internal IDE controller. So we should certainly (and did) back this out for 4.3-RELEASE, but it strikes me that there are two things that may need to be fixed here: 1) It may be that we need a seperate "MAKEDEV all" for each architecture 2) Someone :-) needs to fix ATA to provide the support you need for PC98, as I keep being assured that WD is marching towards destruction. Note that the problem we were trying to resolve with this commit is the following: sysinstall uses libdisk to generate a list of available disk devices. Right now, the default install creates both ad* and wd* device nodes, and sysinstall detects both post-install, so both appear in the drive selection dialog for disk labeling/partitioning operations, which has the potential to cause substantial confusion (as well as possibly have nasty impacts if the user chooses to label / partition both of them independently :-). One way or the other, we need to get to the point where we no longer have both AD and WD lying around, which probably means that all controllers broken in AD need to be fixed, and WD can be removed. It's useful to note that the primary source of problems with AD that I have observed is overly agressive use of DMA instead of PIO for devices that don't support it. I wonder if that's something we could be doing better? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message