The best solution to the sound driver issue, IMHO, is still entirely
just no-one has written it yet.
What we should do:
1. Before auto-unload of the driver, run a small utility which will read
and save them somewhere
2. When auto-loading the driver, use driver arguments which are initialized
settings saved above
All that's missing is the method of passing data from step 1 to step 2.
----- Original Message -----
From: "David Woodhouse" <email@example.com>
To: "Horst von Brand" <firstname.lastname@example.org>
Sent: Monday, November 06, 2000 19:06
Subject: Re: Persistent module storage [was Linux 2.4 Status / TODO page]
> email@example.com said:
> > No funny "persistent data" mechanisms or screwups when the worker
> > gets removed and reinserted. In many cases the data module could be
> > shared among several others, in other cases it would have to be able
> > lo load several times or manage several incarnations of its payload.
> The reason I brought this up now is because Keith's new
> inter_module_register stuff could easily be used to provide this
> functionality _without_ the extra module remaining loaded.
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to firstname.lastname@example.org
> 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@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:19 EST