Date: Wed, 14 Jun 2000 10:31:42 +0200 From: Neil Blakey-Milner <nbm@mithrandr.moria.org> To: Terry Lambert <tlambert@primenet.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Doug Rabson <dfr@nlsystems.com>, Warner Losh <imp@village.org>, Doug Rabson <dfr@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h Message-ID: <20000614103142.A10882@mithrandr.moria.org> In-Reply-To: <200006131628.JAA08308@usr05.primenet.com>; from tlambert@primenet.com on Tue, Jun 13, 2000 at 04:28:58PM %2B0000 References: <8947.960886026@critter.freebsd.dk> <200006131628.JAA08308@usr05.primenet.com>
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. 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). Actually, there should probably be a deviceID- and/or driver-specific way of disabling autoloading or loading of the driver for that device, or that driver at all. I positively disliked it when one of my (PCI) network cards froze my personal (multi-booting) machine on detection and then further probe a long long time ago. Draft proposed loader changes: 'autoloadmodules' can be passed to the kernel by loader, could probably default to 'off' in /boot/defaults/loader.conf, and would be set 'on' for the install case (which would generate the necessary /boot/loader.conf magic in sysinstall and/or another utility to save the current module usage there to work on that hardware next time around), and could be turned 'on' or 'off' explicitly in /boot/loader.conf (possibly by a libh application) or during interactive loader usage. 'autoload_disabled_quiet' could be set possibly by default to 'no', and if set to 'no' would mean that you get the "Uses module \"blaha\"" message (how and whether we detect what modules it belongs to is another story). If we export this information via sysctl, we don't need to reboot with changed loader variables, and can comfortably view them from a userland console utility or libh application. Or, we could reuse "*_load" and company in loader.conf, with existing alternatives 'on', 'off', and a new 'autoload' option. 'autoload' is to auto load if found and 'autoloadmodules' is enabled. 'on' always loads, even if detection fails, and 'off' never loads, as before. All "*_load" options in defaults/loader.conf can default to 'autoload', so that the enabling of 'autoloadmodules' is initially global. (of course, this might not be feasible in BootForth, and then we'd have to add usb_auto_load="YES"/"NO", defaulting to "YES".) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org 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?20000614103142.A10882>