Re: Current git head oops'es at boot on Overo

2008-10-06 Thread Steve Sakoman
On Mon, Oct 6, 2008 at 2:15 PM, Nathan Monson <[EMAIL PROTECTED]> wrote: > 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 disconnectin

Re: Current git head oops'es at boot on Overo

2008-10-06 Thread David Brownell
On Monday 06 October 2008, Nathan Monson wrote: > 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 sid

Re: Current git head oops'es at boot on Overo

2008-10-06 Thread David Brownell
On Monday 06 October 2008, Steve Sakoman wrote: > How does your kernel config set up musb -- host or OTG?  Mine is set up as > host. For now, host-only. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: Current git head oops'es at boot on Overo

2008-10-06 Thread Nathan Monson
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

Re: Current git head oops'es at boot on Overo

2008-10-06 Thread Steve Sakoman
On Mon, Oct 6, 2008 at 12:53 PM, David Brownell <[EMAIL PROTECTED]> 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 th

Re: Current git head oops'es at boot on Overo

2008-10-06 Thread David Brownell
On Monday 06 October 2008, Steve Sakoman wrote: > Build is stock 62c36fdd962de2db5d62a326490913f41c442a5c, no additional > patches. > > Without DEBUG_LL, boot silently fails. With DEBUG_LL, one can see that > the failure is due to a NULL pointer dereference in musb. > > I suspect that the root c

Current git head oops'es at boot on Overo

2008-10-06 Thread Steve Sakoman
Build is stock 62c36fdd962de2db5d62a326490913f41c442a5c, no additional patches. Without DEBUG_LL, boot silently fails. With DEBUG_LL, one can see that the failure is due to a NULL pointer dereference in musb. I suspect that the root cause is related to: <3>i2c_omap i2c_omap.1: controller timed o