Date: Sun, 9 Jan 2000 10:19:01 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: "David O'Brien" <obrien@NUXI.com> Cc: Peter Wemm <peter@netplex.com.au>, "Jordan K. Hubbard" <jkh@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf GENERIC LINT Message-ID: <200001091819.KAA19795@apollo.backplane.com> References: <groudier@club-internet.fr> <20000109144403.E6D8E1CCE@overcee.netplex.com.au> <20000109080852.Q54775@relay.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:On Sun, Jan 09, 2000 at 10:44:03PM +0800, Peter Wemm wrote:
:> > A) Let the 'sym' take precedence over 'ncr' (default)
:>
:> Yes!
:
:I'm personally against this, as I feel it is the wrong thing to do in
:-STABLE. Changing a kernel driver out from under deployed stable systems
:is something we state we don't do. Don't forget it also causes people
:with wired down drive numbering to have to change things if they don't be
:extra carful when merging GENERIC changes into their kernel config files.
:
:Making it so that `sym' handles things that `ncr' does, is of our course
:a good thing to do. Then the user could have both `ncr' and `sym' in the
:config file and keep `ncr' as the driver for what they have today. For
:those with cards that both `ncr' and `sym' support, users can comment out
:`ncr' if they wish to use `sym'.
:
:--
:-- David (obrien@NUXI.com)
Don't we still have the issue of the ncr<->fxp interaction causing
crashes? I was under the impression that this problem didn't occur
with the sym driver and because of that the sym driver was given
precedence...
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001091819.KAA19795>