Persisting driver configuration

[Dan Nicholson]

On Mon, Jul 14, 2008 at 3:35 PM, Peter Hutterer
<peter.hutterer at who-t.net> wrote:
>
> For server 1.6 onwards device properties are the way to go. Simply make the
> driver expose appropriate properties and a client can change them at run-time
> to any value.
> Of course this isn't persistent either and needs to be re-set after server
> reboot, but at least it allows you to re-set the values.

So, in the bright future, would the preferred plan be to store the
properties in, say, gconf, and apply them per-session? Or to try to
apply them per-device in a HAL fdi?

--
Dan