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 > 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: - CONFIG_USB_MUSB_AM35X=y + # CONFIG_USB_MUSB_AM35X is not set + CONFIG_USB_MUSB_OMAP2PLUS=y -- balbi -- 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
