Messages in this thread |  | | Subject | Re: Proposal for cleaning up kernel driver parameters | Date | Thu, 12 Dec 96 15:54:25 PST | From | Craig Milo Rogers <> |
| |
>I've been thinking about how to best implement a "unified" way of >setting driver parameters for kernel-resident and modularized drivers ... >-- Treat the boot command line as a set of environment strings for the
If there were a single kernel envar pool, and if drivers were allowed to putenv() as well as getenv(), it could be a unified way to save configuration information across module incarnations, or even across system reboots. This raises the usual questions about built-in drivers being able to autoprobe and/or configure multiple devices, and whether or not module-based drivers can do the same; the envar naming convention is important here.
Presumably a "/proc" device could be used to handily view and edit the kernel envars.
Craig Milo Rogers
|  |