On Tue, 28 May 2013, victor yeo wrote: > Now the UDC driver is working on both Linux and Windows host, meaning > the read/write operation is ok. I still use the polling method, > because waiting for interrupt is not reliable. Why aren't the interrupts reliable? Is this a known erratum for your hardware? > Is it possible to > contribute the code to Linux community? Yes. But first you should test it with other gadget drivers, not just g_file_storage. > On the other hand, i run the USB 2.0 command verifier to test the > gadget, the gadget crashes at BOS descriptor test. I think the gadget > is not able to handle BOS descriptor, is the gadget driver setup > function returning negative error code for BOS descriptor? The crash dump you attached contained this line: PC is at kagen2_irq+0x290/0x3bc [kagen2_udc] This means the crash occurred inside the UDC driver, not the gadget driver. Alan Stern -- 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
