Marcel Holtmann wrote:
Hi David,
It will make the driver more complex and I don't think it is needed.
It's needed, but it's not very complex. Just define a work_struct,
initialize it with a routine that calls usb_set_configuration(),
and schedule_work().
but I have to redesign my probe() routine. The USB core will call
disconnect() and probe() again, right?
Yes. You can't quite tell the "needs firmware upload" case
apart from the "firmware already loaded" case by looking at
its descriptors, can you? Most of the other USB firmware update
schemes try to ensure that's visible from the descriptors.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
