From owner-cvs-all Sun Jan 9 15:15:24 2000 Delivered-To: cvs-all@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BCDA014E06; Sun, 9 Jan 2000 15:15:17 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA30745; Sun, 9 Jan 2000 15:14:20 -0800 Date: Sun, 9 Jan 2000 15:14:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: Peter Wemm , "Rodney W. Grimes" , obrien@NUXI.com, "Chris D. Faulhaber" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC LINT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > On Sun, 9 Jan 2000, Matthew Jacob wrote: > > > > Hmmm... In fact this patch hasn't the expected effect :). I didn't provide > > > a better one since nobody seems to need to configure both drivers. > > > > Don't both drivers have to configured in the GENERIC case? > > Only the support for the C1010 requires both driver to be configured > in GENERIC since it is the kernel that will be used for installation. > > For now, my understanding of the situation is: > > 1) 4.0 has appropriate flags to deterministically know about the driver > the kernel will use for each 53c8xx chip when ncr and sym are > configured. > 2) next release is 4.0 > 3) 3.4 is out of the door without the sym driver. But the sym driver is in the RELENG_3 branch, so one way or the other an INSTALL kernel will be built in 3.X with the sym driver. > 4) It has been reported that the actual order drivers are probed > relies on /conf/files order and this probably will not change in > later 3.X kernels until 4.X will be preferred by users. > > If (4) is ok, then no need to go with a patch, in my opinion. If (4) is > untrue, some tiny patch, similar to the one that had been proposed, > applied to one of the driver should fit. If the sym driver has to be > modified, this will not make problem. But a clear decision has to be > taken, and I am waiting for this to occur. I believe that if there is support for both SYM and NCR drivers, than for whatever release they are integrated in they should *by default* not overlap in device support (that's a problem with NCR, not SYM). If some users wish to exclusively use NCR instead of SYM, say for an 83c75, a config option to re-enable this support is appropriate. In either case, NCR needs to be modified so sanity happens. The trouble is that the nominal owner of NCR, Stefan Esser, doesn't seem to be involved here- otherwise any one of you, David O'Brien, Me, Rodney, whomever, can just do the right thing. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message