Andreas Kemnade wrote: > > I have looked again into the logs and wonder why you think > the first control transfer fails. It is completed after 15 seconds when it times out and is cancelled. > It gives EINPROGRESS as error which does not make sense at all IMHO > in blocking io. I would understand things like ETIME, EPIPE, > ENOENT but not EINPROGRESS. So perhaps the control transfer was > successful, but usb_control_msg did for some reason not wait for the > result. The result code of cancelled transfers may just be set wrong. > I have never seen EINPROGRESS on usb_control_msg() on wired USB, either. > So I think there are still issues to look at without rf sniffing > equipment. But where does EINPROGRESS come from? Feel free to investigate. David -- David Vrabel, Senior Software Engineer, Drivers CSR, Churchill House, Cambridge Business Park, Tel: +44 (0)1223 692562 Cowley Road, Cambridge, CB4 0WZ http://www.csr.com/ Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom -- 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
