On Thu, 31 Jan 2008, Salvador Eduardo Tropea wrote: > 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).
That's why the reset code includes several retries. > 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. > 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. When a reset fails, the kernel should do exactly the same thing as if the device was unplugged. Are you saying that it doesn't? Alan Stern - 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
