Date: Tue, 13 Jun 2000 09:48:31 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Warner Losh <imp@village.org> Cc: Doug Rabson <dfr@freebsd.org>, arch@freebsd.org Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h Message-ID: <Pine.BSF.4.21.0006130947450.68954-100000@salmon.nlsystems.com> In-Reply-To: <200006130621.AAA12159@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jun 2000, Warner Losh wrote: > In message <200006091600.JAA25038@freefall.freebsd.org> Doug Rabson writes: > : dfr 2000/06/09 09:00:31 PDT > : > : Modified files: > : sys/pci pci.c pcisupport.c pcivar.h > : Log: > : Nuke the useless chip driver. It gets in the way when you want to load > : a functional driver for the device. > : > : Revision Changes Path > : 1.153 +2 -1 src/sys/pci/pci.c > : 1.163 +3 -51 src/sys/pci/pcisupport.c > : 1.46 +2 -1 src/sys/pci/pcivar.h > > Personally I think that we should add it back as a "loose" or > "generic" device after I finish the work on the unknown driver. This > would allow you to do the same thing, and still have decent boot > messages. As I said on in a reply to committers, this is probably best handled by the nomatch method of the pci driver. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0006130947450.68954-100000>