On 2007-01-25, Oliver Neukum wrote: > Am Donnerstag, 25. Januar 2007 01:21 schrieb Oleg Verych: [] >> Ehh... USB, Devices are designed to change configurations, linux-usb isn't. >> Without much technical details -- this is a bed design. No? > > It is designed to change configurations through sysfs or usbfs. It's not > designed for a driver to change configurations. Drivers are for interfaces. > Interfaces have no configurations, they have settings. These a driver can > change.
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. p.s. song about why ti-usb's firmware is in os-space, while there at least 2 ROMs are in device, is more damn ugly. ____ ------------------------------------------------------------------------- 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
