On Tue, Dec 18, 2012 at 12:32 PM, Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx> wrote: > On Tue, Dec 18, 2012 at 10:28:18AM -0600, ricardo garcia wrote: >> > try with our test application just to rule out bugs on the host side. >> > Also, which controller are you using ? Why are you sticking to such an >> > old kernel ? Can you try with current stable release, v3.7 ? > > That is a good start :) > >> > v3.0 was release Jun 2011, that's really old. If you can't upgrade your >> > kernel, you will have to ask for support from whoever gave you such old >> > release. >> > >> > -- >> > balbi >> >> >> How do I find the controller that im using? this is an embedded system... >> Linux 3.0.17 #8 PREEMPT Tue May 15 08:00:00 MST 2012 armv6l GNU/Linux >> i will try to compile a 3.7 kernel > > v3.0 is before udc-class got merged. There are two ways: > - look for the "manufacturer string". This should be something like > "usb 1-1: Manufacturer: Linux 3.7.0+ with dummy_udc" > The part after "with" should tell you the name of the udc. > - check your .config which UDC driver has been enabled. Back in v3.0 it was > only possible to enable one. > - a third way might be to enable debug and look which drivers are loaded after > "modprobe g_zero" and what output you get. Sometimes it prints the driver > here or there. > > Sebastian my controller its: PHY dwc_otg (Broadcom BCMxxx) im not currently able to test this with 3.7, can somebody give it a try to rule out that its a software problem??? (try sending more than 128 bytes to the loopback gadget driver function within g_zero and see if you receive it back...and trying with 256, 512 , 1024 and 4096 buffer sizes would be nice as well.....please and thanks -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
