On Mon, 28 Mar 2011 11:37:22 +0300, Felipe Balbi <balbi@xxxxxx> wrote: > Hi, > > On Sat, Mar 26, 2011 at 07:42:34PM -0400, Ben Gamari wrote: > > Today I've had a very frustrating time trying to bring up a BeagleBoard > > (arch/arm/mach-omap2/board-omap2beagle.c) with the 2.6.38 > > there's no board-omap2beagle > My apologies, s/omap2/omap3. > > kernel. Unfortunately musb has been giving me great difficulties, > > > > # modprobe g_ether > > [ 25.276855] usb_gadget_probe_driver 1815: usb_gadget_probe_driver, no dev?? > > modprobe: Failed to load module g_ether: No such device. > > > > After a great deal of printking, I've determined that the error is > > coming from platform_driver_probe (platform.c:499). The code in question > > appears to be a check ensuring that any devices being probe were first > > registered. When the musb-hdrc module is probed, this check seems to > > fail with code = 1 and list_empty(&drv->driver.p->klist_devices.k_list) > > = 1. > > looking at your .config from previous mail, it's wrong. You're trying to > use am35x glue layer while you be using omap2430, just change: > Alright, fair enough. The mishmash of IP found in these ARM devices can make it very difficult to determine the correct configuration at times. Thanks for your help! - Ben -- 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
