I'm set up as host, using a BeagleBoard, and with the current linux-omap git I can get USB working by unplugging and replugging the A side of the cable (at the mini-AB connector on the BeagleBoard). Just disconnecting the cable at the B side is not enough. It must have something to do with the ID pin. So, if you have a soldered ID pin it wouldn't work either. Also, my cable is going into a powered 4 port high speed hub. That might make a difference. - Nathan On Mon, Oct 6, 2008 at 2:04 PM, Steve Sakoman <sakoman@xxxxxxxxx> wrote: > On Mon, Oct 6, 2008 at 12:53 PM, David Brownell <david-b@xxxxxxxxxxx> wrote: >> On Monday 06 October 2008, Steve Sakoman wrote: > >>> However unlike others, I find that musb is not functional -- and the >>> trick of disconnecting the USB cable and then reconnecting it does not >>> work. >> >> I observed the same thing. More specifically, no IRQs arrive at >> the twl4030-usb driver. >> >> The *very same kernel* works fine on Beagle... is there something >> different about the USB setup that might explain this? > > I took a look at the schematics for that section of both boards and as > far as I can tell the two boards are identical in their omap/twl4030 > interconnect for the musb section. The linux board files are > extremely similar too -- nothing significant as far as I can tell. > > I tried the same experiment and used my Overo kernel on Beagle. I got > exactly the same behavior on Beagle as I did on Overo. So my results > are different than yours. > > How does your kernel config set up musb -- host or OTG? Mine is set up as host. > > Steve > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
