So, in short, what I'd like to do is somehow force my device to an address that I choose. I've been exploring this and tried just adding a special case into usb_choose_address(), only to find that the host hasn't pulled the device descriptor information yet (which I'd need to compare the VID/PID to my failing device - interesting, since Windows gets the device descriptor before doing anything). The obvious solution
USB allows both sequences; Linux has used that approach for years now without evident problems.
to that was to try pulling out the device descriptor first but that appears to fail with ENODEV if you're trying to talk to address zero.
Where does that ENODEV come from? You might have made that change wrong; the code I noticed would reject requests before the device reset finished, but explicitly allows control traffic in DEFAULT (address==0) and ADDRESS (before CONFIGURED) states.
You certainly _should_ be able to put together a hack like that.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
