Mahlzeit
Still at the same problem. On one PC debug output in usb-uhci dies help against the timeouts (with the packet sliding effect) on a second PC not. The current workaround is, that the reader get's a reset command, which tells the reader to reset its USB interface chip. On the first PC this works wonderfull, i.e. a device disconnect/attack is initiated by this and after that, the device can be used as normal. (Until the next timeout.) On the second PC the disconnect/attach sequence is not always executed. After an erroneous reset writes to the reader fail with "already writing". Any idea what could happen there? Thanks endergone Zwiebeltuete ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
