David Brownell <[EMAIL PROTECTED]> writes: >> When this get device info function returns to my probing function I >> assume I really do have a device I'm going to keep. So, I submit the >> interrupt urb. At this point, the submission fails with an -ENODEV. >> What this likely means is that either I don't have a urb, or the urb's >> usb_device pointer is bad. I can't figure out why either would be the >> case. If someone smart could take a look at my code or my logic >> described here and tell me why I'm loosing my device I'd appreciate >> it. > > I had no particular insights from skimming your code. When you apply > judicious dbg() printfs, what does it tell you about why that failed? > Or if you're a debugger user, you can set breakpoints .. :)
Stupid typo. My init_endpoints_dp() wasn't identifying the interrupt endpoint. It never got initialized, so the urb submission rightly failed. Sorry to waste bandwidth. -- (__) Doug Alcorn - Unix/Linux/Web Developing oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ mailto:[EMAIL PROTECTED] http://www.lathi.net ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
