Am Samstag, 8. Januar 2005 18:52 schrieb Alan Stern:
> Thirdly the memory image is restored and the driver in the image is
> running again. Now it may have to take control of the HC from the BIOS,
> from nobody (but after the HC may or may not have been reset), from its
> duplicate in the startup kernel, or from its own former incarnation. And
> it's not so easy to tell which has happened! Fortunately, all it really
> needs to do is another BIOS takeover (if needed) and decide whether a
> reset is required (that's the hard part).
Upon further reflection, in a statically compiled driver you know
you are taking over from yourself, already at compile time.
Regards
Oliver
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
