On Saturday 06 September 2008, Steve Sakoman wrote: > On Fri, Sep 5, 2008 at 10:52 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Steve Sakoman <sakoman@xxxxxxxxx> [080905 10:24]: > >> > Hmm, is the musb broken now? > >> > >> It is on Overo if I base my patches against current top of tree > >> (a376251519ced5831ed07ed234430725230ed93a) > >> > >> Doesn't crash, just quietly doesn't work. I hear from Beagle folk > >> that musb doesn't work there either. ... A while back I tried a patch making the rc3-omap code match mainline (more or less) on Beagle, and it failed ... so I've been tracking down various RC3 issues. I don't have all of them yet, but various "used to work" (on DaVinci and TUSB6010) scenarios -- plugging/unplugging the B side of a cable (Beagle == host), reboot with cable connected (Beagle == peripheral) are being trouble. There's also a notification issue with CDC Ethernet ... if the usb0 interface (Beagle == peripheral) is brought up before the host gets connected, the host can't talk to it. I just sent that patch in: http://marc.info/?l=linux-usb&m=122076214105934&w=2 > Mans has a patch in his git: > > http://git.mansr.com/?p=linux-omap;a=commitdiff;h=1e5bc41773bb981b3a89bd762becf98c72be5e4c > > Neither of us understand musb details enough to propose this as *the* > fix, but it seems likely to be the issue. Missing that should probably make trouble, yes. -- 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
