> > Question: why did the first urb complete with -EILSEQ when
> > the other device was plugged in?
>
> And also, why did it _keep_ doing that afterwards?
This is presumably the same question.
> A quick glance at usb-uhci.c in 2.4.19-pre10 makes me
> wonder what other status bits might be set when it
> reports that.
>
> Can you tweak the "return -EILSEQ" to be more like
>
> { info ("status bits %08x", status); return -EILSEQ; }
>
> and see if perhaps some other status bit is more suggestive
> of the real problem. Maybe the data toggle got trashed, or
> something similar.
This always gives "status bits 00440000".
All the best,
Duncan.
PS: If I stop the user space driver (which is submitting urbs madly)
then the problems stop also.
PPS: The user space driver submits on average 3 urbs per jiffy,
which is about 1 every 3 milliseconds, which is ok since I am told
the USB 1.1 spec states you shouldn't poll an interrupt endpoint faster
than 1 poll per millisec.
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
