[lkml]   [1996]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Proposal for cleaning up kernel driver parameters

    >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

     \ /
      Last update: 2005-03-22 13:38    [W:0.018 / U:1.096 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site