I've seen the same arguments over and over again here. It seems that there
are two feasible ways to accomplish persistence: totally kernel and
totally user-space
The totally kernel-space people want to make a way for modules to store
persistent data, either in memory, or across boots on disk. These people
seem to debate whether modules should be unloaded/loaded upon suspend/resume.
Among the user-space people, there are some who want the status quo, where
the driver initializes the card, and then a user proggy sets it up the way
it really should be, which causes the gap problem.
There was also a suggestion (which sounded pretty interesting) where the
driver would not initialize the card until prompted to do so by a
user-space program, which would also give it the correct settings. It
seems that the big problem with this is that the card may not get
initialized when it needs to be. The initialization/state-saver proggy may
have to be called: on boot, on suspend, on restore, when the hardware is
physically removed and replaced, when something goes wrong and the user
wants to reset things, and on shutdown.
I just wanted to try to get all the arguments together on one page. I hope
I didn't miss anything, or make any big mistakes. My own guess is that the
first option is the most reliable, and that the last one is the most flexible.
--
This message has been brought to you by the letter alpha and the number pi.
David Feuer
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
