moderate persistence of module configuration??

Dan Miner (dminer@nyx.net)
Wed, 28 Feb 1996 22:10:56 -0700 (MST)


I've been play with modules quite a bit and liking them more
and more. I really like the automatic load/unload of them too.
However, I have found a couple of questions I'd like to bring
forward. If the answers exist then by all means point me to the
document or archive.

1) After loading a module with device autodetection and unloading, there
appears to be no way for the module to reference that previously known
information to speed up autodetection.

2) For the first loading of a modular device driver, how can I pass it
parameters for easier detection of the hardware (may be required in
some cases). Example, boot parameters are passed to these drivers
when compiled into the kernel. I do not see any modules referring
to the stored options on initialization of itself as a module.

Trying loading and unloading the sbpcd driver and your hardware
is detected on the 5th probe. [I know.. load it and don't unload
it.. :)] I think this ability to inform drivers may come in handy
in the future.

Regards,
Dan

-- 
Dan Miner					dminer@nyx.cs.du.edu
	"The longer I stare at this screen; the blanker it gets."
						Linux: try it, you'll like.
"Your program is encoded in pi."		I started with a 64