Yeah, I hacked that in the hh.org tree to support multiple platforms. (ie machine_is_xxxx)
Hmm, I just saw that. It's not so much supporting multiple "platforms" (which this code has always done) as choosing between the boards at runtime, using different GPIOs. So the same kernel might run on an h1900, h3900, c750, and so forth -- all wired differently.
I'd like to merge such support, but ... where do the machine_is_xxx() macros come from? Grep turned up neither definitions nor declarations.
No sooner did I post my response than did I realize this that that may all be well and good, but that's not the problem I'm seeing - the problem I'm seeing is that even when the USB cable is manually disconnected and reconnected, my gadget driver does STILL not detect that it's been connected. Again, thoughts?
Turn up the debug and see whether you're getting IRQs at all; you should be getting at least SUSIR/RESIR on disconnect/reconnect. And then RSTIR if the host sees and resets the device.
Do you know for a fact that the host sees a device? I could very easily imagine there's another GPIO involved. Maybe you have to retrigger something. This is specific to the h3900, yes?
- Dave
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
