Hi Alan, > It is a bug in the Titanium firmware. In the logs for both handhelds you > can see where the kernel sends a Set-Interface request after your driver releases the interface. (The kernel does this automatically so that the interface will be back in its original condition when the next driver binds to it.) Both devices return an error, which is a perfectly legal response. > > However the Titanium then crashes. It doesn't respond to the Clear-Halt commands sent by the kernel after the Set-Interface fails, whereas the TI84+ acknowledges them correctly. Since it has crashed, your driver is unable to reconnect and you have to reset the device by unplugging it. > > The source of the errors is the Titanium failure to respond to the kernel's Clear-Halt requests.
I have a burning question: why Linux does not handle this behaviour while Windows does not reject it? Can I handle this 'quirk' directly in my tiusb kernel module or is this behaviour managed in the USB core (and thus, not accessible from an upper level)? I'm not a USB-internals guru ;-) > Alan Stern Regards, Romain. ------------------------------------------------------------------------- SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
