David Brownell wrote:
Hi Alex,
I just tried this with the version pulled off the bk gadget-2.6 tree today. It worked fine for me over both full- and high-speed, except I had to swap those two VID/PID device entries in linux.inf to get it to enumerate. I haven't looked into why there's a discrepancy there...
Well, that should be something of a problem! The devices should all be using the 0xa4a2 ID now, not 0xa4a1 ... I guess that problem doesn't show up on all versions of Windows, it certainly didn't show up in the minimal testing I did.
For the record I was running XP Pro SP1. Also, things got kind of flaky later on. It seemed to have killed something in the Windows driver handling (the device always showed up in device manager even when I unplugged it and it wouldn't re-enumerate when I moved it to various ports). That was cured when I rebooted the host (things worked fine from there) but then when I yanked on the USB cable my host came up with a BSOD on usb8023.sys. That said I have no idea what caused it (device problem or host), but maybe someone who knows something more about RNDIS and how that gadget works would be interested....
Thanks for checking, and finding that issue! FYI the same code is now in the gadget-2.4 tree too ... including that new library code to help autoconfigure drivers (mostly to let gadget drivers pay less attention to the hardware).
Cool, saw the traffic about that on linux-usb-devel. It'll be good to be rid of the #if ugliness.
alex
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
