On 30/01/08 14:05, Alan Stern wrote: > It's a bug for Set-Interface to fail.
Yes and not. > Following a reset, the device has no reason to fail such a request. > The device doesn't, but you can lose a packet (i.e. CRC error). In this case the kernel should properly recover. In this case the kernel is recovering, but the hiddev becomes useless because the device changed its address. I think the kernel should make this device invalid and inform a read error as soon as the user space tries to read from it. I think the application gets notified only if reading in blocking mode. > I'm not terribly familiar with the hiddev driver, but I think it's not > a bug that it doesn't report any kind of read error when this happens. > The situation should be exactly the same as if you had unplugged the > HID device -- reads should return an end-of-file indication rather than > an error. However I could be wrong about this. > It currently informs an error if the device is unplugged. IMHO that's the right thing to do, the user space application can then close the file handle and try to open it again, if it fails the application can then try to interact with the user asking to replug the device. Regards, SET -- _______________________________________________________________ Ing. Salvador Eduardo Tropea http://utic.inti.gov.ar/ INTI-Electrónica e Informática Tel: (+54 11) 4724 6315 Colectora de Av. General Paz 5445 San Martín - B1650KNA Casilla de Correo 157 FAX: (+54 11) 4754 5194 Buenos Aires * Argentina http://www.inti.gov.ar/ - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
