Hi, I'm having trouble porting our in-house UDC driver to 2.6.27. It originally worked on 2.6.14 as an CDC-ACM driver. I notice a lot of changes since 2.6.14. For starters, instead of the single serial.c file, there is now f_serial.c, u_serial.c and f_acm.c. Currently, the UDC driver in 2.6.27 seems to work if I simply plug the USB cable in between our gadget serial Linux device and a Windows PC. However, if I unplug, then replug the cable, the 'Out' Endpoint seems fine, but the 'In' Endpoint doesn't seem to come up properly. In other words, data only seems to be getting through in the direction from the PC to the gadget serial Linux device, but not vice versa. Is there some sort of architecture document to show how the f_serial.c, u_serial.c and f_acm.c files all fit together? I've searched in the Documentation directory and I've read the usb-gadget-serial docbook document but it doesn't really tell me this. Also, it seems that for some reason composite.c is being compiled and used, but my CDC-ACM gadget serial driver is *not* a composite driver. Is it possible to prevent linking with this composite driver? Cheers, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
