> How about a standard API where a module can save/restore any number of
> settings between sessions. The module will simply call somethings like
> save_settings (int id, void *buffer, in size)
> where the id allows a module to save multiple buffers. The info will be
> saved and later the module (when loaded) can request the settings with a
> similar 'get_settings' call.
This looks like the right way to implement persistent data for drivers.
However I prefer using a string ad the 'id'. In this way less
administrative work is required to prevent conflicts between drivers/modules.
Hannu
-----------------------------
Hannu Savolainen (hannu@voxware.pp.fi, hannu@4front-tech.com)
http://personal.eunet.fi/pp/voxware/hannu.html (my home page)
http://www.4Front-Tech.com/uss.html (UNIX Sound System (USS))
http://personal.eunet.fi/pp/voxware (USS Lite/TASD/VoxWare)