Hello again Alan, we read that the patch broke. Damn, our fear was justified. If we are right, it will break again because it affects various devices using different busses, each one with its limitations and defects. That's why we wrote to Sarah(and got no reply yet) that vendors should fix their h/w bugs in-house or give open source developers full documentation (like nda datasheets,bios spec,bios spec up) to cope with their >buggy< hardware! > Probably it is cured. But something is still wrong, even though it may > be unrelated. Since something is broken and the last program tested exits at A50M, we have some questions for today prior testing A50M, moschip and ICH4M: 1)Do we need to apply a third patch(http://marc.info/?l=linux-usb&m=136379040918329&w=2) [it's upper part to be specific]? If yes, please make a cumulative patch for 3.8 series before we mess things up and post it under this subject. At the same post, add the final test program with program version number printing as well as a "do NOT unplug the usb and a leave the program to go up to 1000" message. Also point out that the device must not be inside the unusual devs file as you told us. This will make it easier for others to follow and help you. 2)If A50M still fails, do you have time to analyze our usbmon output? 3)Has any type of transfer corruption been observed from this bug? -- 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
