Re: omap udc driver problem with beagle board
2010/5/30 Felipe Balbi m...@felipebalbi.com: On Sun, May 30, 2010 at 11:53:49AM +0200, Marco Stornelli wrote: beagle board uses musb. You shouldn't be relying on the udc controller. Your Kconfig is just wrong. -- balbi Oops, my fault. I see the error in the configuration. Thank you very much for your response. I'll try again. Regards, Marco -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omap udc driver problem with beagle board
On Mon, May 31, 2010 at 09:06:35AM +0200, ext Marco Stornelli wrote: Oops, my fault. I see the error in the configuration. Thank you very much for your response. I'll try again. no problem. -- balbi DefectiveByDesign.org -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
omap udc driver problem with beagle board
Hi, I'm using the kernel 2.6.34 with the beagle board rev. c4. I have got some problems with the ethernet gadget to use nfs over usb. The problem is with the usb. When the g_ether driver register itself, the omap udc driver returns ENODEV because the kernel didn't call the probe for this driver. Looking at the code, it seems the problem is in board specific management of the usb. There isn't the registration of the platform device to match the omap udc platform driver. It should be done in the omap_usb_init() but in case of beagle board this function is never called, so omap udc driver cannot work. Is it a regression? Is there any workaround? Thanks. Regards, Marco -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
