Persistent module storage [was Linux 2.4 Status / TODO page]
This sounds to me like the most flexible way to do it. If the module accepts parameters then those who want the sound card initialized at every load can put the desired settings in modules.conf. The rest of us can just initialize it once at boot time and the rest of the time the settings will be left untouched.
James A.Sutherland <[email protected]> on 11/06/2000 11:38:44 AM
To: Alan Cox <[email protected]>, [email protected] (James A. Sutherland)
cc: [email protected] (David Woodhouse), [email protected] (Jeff
Garzik), [email protected] (Dan Hollis), [email protected] (Alan Cox), [email protected] (Oliver Xymoron), [email protected] (Keith Owens), [email protected] (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: Persistent module storage [was Linux 2.4 Status / TODO page]
Quoted 1 line · Alan Cox
Quoted 1 line
So autoload the module with a "
dont_screw_with_mixer" option. When the
kernel
Quoted 7 lines
Quoted 3 lines
first boots, initialise the mixer to suitable settings (load the module with "
do_screw_with_mixer" or whatever); thereafter, the driver shouldn't change the mixer settings on load.Which is part of what persistent module data lets you do. And without having to mess with
dont_screw_with_mixer(which if you get it wrong btw can be fatal and hang the hardware)
Eh? You just load the driver once, probably on boot, to configure sane values. This time round, you use an argument (or an ioctl or whatever) to specify the values you want. (cat /etc/sysconfig/sound/defaultvolume > /dev/sound/mixer or whatever). After that, the module can be unloaded and loaded as needed, without any need to touch the mixer settings except in response to *explicit* "set volume" commands from userspace.
James.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/