Marcel Holtmann wrote:
is there a problem with re-exporting it?
Other than through sysfs (or usbfs) you mean? Mostly
just locking implications.
What happens if you usb_reset_device() after loading the firmware?
Ideally that'd turn up new descriptors and the device could be made
to select the "right" config right away.
I can't tell you that right now, because the 2.4 version was different
and I haven't used the usb_set_configuration() call outside the probe()
routine. My plan is to do it this way:
I meant use reset_device() INSTEAD of set_configuration().
How does this hardware act ... does it look different (most
common model) or not?
probe()
switch (configuration)
case 1:
load_firmware()
schedule_work()
set_config(2)
case 2:
register_device()
Or alternatively, as I suggested at one point:
dev_setup()
load_firmware()
return 2
probe()
fail if config != 2
register_device
That is, add a new driver call and its usbcore support.
I suspect other drivers may have similar problems, even
though I think most other firmware loaders would have
their dev_setup() calls just use usb_reset_device().
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
