tom.leiming@xxxxxxxxx wrote: > From: Ming Lei <tom.leiming@xxxxxxxxx> > > This patch introduces isochronous source sink function driver > into zero composite driver. The driver is based on David Brownell's > f_sourcesink.c > > It can be used to evalute isochronous transfer performance of usb > host controller or usb host controller driver, or can be used to > troubleshoot usb host controller driver(usually some embedded hcd) > or usb gadget controller driver handily, or can be used to test gadget > driver or hardware. > > It has been verified OK on omap3-based beagle board, and Martin > has tested it OK on other usb gadget controller. > > Basic features supported now: > -multiple interface altsetting > -customization of interface altsetting via module parameter > -single iso-in or iso-out only endpoint > -double buffering or more > -high bandwidth endpoint > > Tested-by: Martin Fuzzey <mfuzzey@xxxxxxxxx> > Cc: David Brownell <david-b@xxxxxxxxxxx> > Signed-off-by: Ming Lei <tom.leiming@xxxxxxxxx> Hi, I tried this out with a net2280 device connected to an OHCI port. usbtest.ko refuses to bind to the device with the following error message. The host is an OMAP board running v2.6.35. [ 1697.512756] usb 2-2: new full speed USB device using ohci-omap3 and address 5 [ 1697.750000] usb 2-2: not running at top speed; connect to a high speed hub [ 1697.776031] usb 2-2: New USB device found, idVendor=0525, idProduct=a4a0 [ 1697.783020] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1697.790466] usb 2-2: Product: Gadget Zero [ 1697.794647] usb 2-2: Manufacturer: Linux 2.6.31.14-net2280 with net2280 [ 1697.801513] usb 2-2: SerialNumber: 0123456789.0123456789.0123456789 [ 1697.813415] usbtest 2-2:4.0: couldn't get endpoints, -22 [ 1697.818969] usbtest: probe of 2-2:4.0 failed with error -22 Is this expected behavior? If not, let me know how I can help debug. - Anand -- 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