Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> Anytime a SET_CONFIGURATION is sent to the device without being preceeded
> by the secret vendor specific command the device reverts to the previous
> device descriptor data indicating 100ma. A normal reset causes it
> to default to the normal power setting.
>
> So, my basic problem is that the Linux USB core does the SET_CONFIGURATION
> as part of device initialization after the device is plugged in, long
> before my driver is probed. I never get the opportunity to send
> the secret command to the device. If I actually write the secret
> command followed by a SET_CONFIGURATION from my driver the BB device
> will reset itself but the Linux core does another SET_CONFIGURATION
> upon seeing the reset and so the hidden device descriptor data has
> reverted back to the low power setting.
Does it work if you issue the secret command, wait and then reset the device
in your probe method?
Regards
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
