Messages in this thread |  | | From | "Alon Ziv" <> | Subject | Re: Persistent module storage [was Linux 2.4 Status / TODO page] | Date | Mon, 6 Nov 2000 19:25:22 +0200 |
| |
The best solution to the sound driver issue, IMHO, is still entirely userspace--- 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 mixer settings and save them somewhere 2. When auto-loading the driver, use driver arguments which are initialized from the settings saved above All that's missing is the method of passing data from step 1 to step 2.
----- Original Message ----- From: "David Woodhouse" <dwmw2@infradead.org> To: "Horst von Brand" <vonbrand@inf.utfsm.cl> Cc: <linux-kernel@vger.kernel.org> Sent: Monday, November 06, 2000 19:06 Subject: Re: Persistent module storage [was Linux 2.4 Status / TODO page]
> > vonbrand@inf.utfsm.cl 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. > > > -- > dwmw2 > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.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 majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |