Am Donnerstag, 25. Januar 2007 15:28 schrieb Oleg Verych:
> When i've known how USB defines firmware updates:
> -- device appears with one firmware-loading ID;
> - after loading it disconnects, and reconnects;
> -- new bus connect event, new ID, same hardware-device still plugged;
> -- (TI USB) is set up with bloody configuration #1, while just
> uploaded firmware operates with configuration #2!
>
> It's complete hardware setup of plugged device. WFT userspace doing
> here? Before i've posted request_firmware() update -- *nothing*!
> That is why i feel design, and your note is somehow wrong.
Yes, there is something wrong with the design of this device.
For these cases there's
int usb_driver_set_configuration(struct usb_device *udev, int config)
You check the current configuration probe() is called with, call
this helper function and exit with an error from probe.
HTH
Oliver
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
