Date: Thu, 15 Jun 2000 22:06:42 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: nbm@mithrandr.moria.org (Neil Blakey-Milner) Cc: tlambert@primenet.com (Terry Lambert), phk@critter.freebsd.dk (Poul-Henning Kamp), dfr@nlsystems.com (Doug Rabson), imp@village.org (Warner Losh), dfr@FreeBSD.ORG (Doug Rabson), arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h Message-ID: <200006152206.PAA12480@usr08.primenet.com> In-Reply-To: <20000614103142.A10882@mithrandr.moria.org> from "Neil Blakey-Milner" at Jun 14, 2000 10:31:42 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue 2000-06-13 (16:28), Terry Lambert wrote: > > > "Found <FOOcorp magicchip 1242> Configure \"blaha\" driver in your kernel" > > > So would just loading the frigging driver from the modules directory, > > instead of beating the user over the head to do it for you. > > That would be nice, of course. So long as there's a way from stopping > the kernel from loading a module you know is broken, and that will > repeatedly crash your system over and over again. rm /modules/broken.ko > Fallback may be: "Uses module \"blaha\", autoloading disabled" with "for > this device" or "for this driver" or "globally". Again, it may be > better, or also, handled by a userland utility (with extension to a libh > interface). That will not work for boot devices. The current loader scheme will work for boot devices. Ideally, for PC hardware, you would use BIOS I/O until you identified the hardware, and then replaced the drive. Windows has done this since Windows 95. [ ... Draft proposal ... ] Looks good, with the caveats, above. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?200006152206.PAA12480>