-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Those aren't that common. The hardware is _never_ supposed to
> be reporting SET_ADDRESS requests, but apparently it's done so
> forever (no erratum).
Thank you, Intel. :)
> I wonder if the handling of that misbehavior is causing some
> lost synchronization, then more trouble later on. Robert Schwebel
> reported a problem in some enumeration testing. I saw some too
> for a while -- but they stopped, so I never changed SET_ADDRESS
> response logic to jiggle IPR/OPR like SET_{CONFIGURATION,INTERFACE}
> now do. That jiggling made a lot of wierdness go away...
It seemed to me like a timing bug, after closer exploration of what the driver
was actually trying to tell me. (PC sends a packet back before we get a
chance to finish off... Your ZLP theory sounds right, testing it now.)
> The "premature status" is presumably for that fetch of the config
> descriptor (80.06/0200) ... and the next request will be automagic,
> SET_CONFIGURATION. I wouldn't rule out the hardware already
> having completed handling the set_config processing before the
> driver noticed anything happened, especially if the host is
> not actually reading the ZLP.
Some printk'ing shows that indeed the request's .bRequest field was
SET_CONFIGURATION. Should we be passing that through as if we were in the
idle state?
> Minor experiment: Pad out that descriptor by tagging another
> descriptor at the end, maybe a vendor descriptor, less than
> 16 bytes (maxpacket) long. This can rule out strangeness caused
> in the "expect to write a ZLP" codepaths. Leaving, I'd hope,
> only strangeness caused by set_address ... and nothing else!
Doing so.. I added an invalid descriptor (type 0x09), not quite knowing what
you meant by a vendor descriptor.
.. Yes, looks like that fixed the prematureness. That's of course a bad hack,
which I would like to avoid. I'll try adding better support for SETUP packets
that come when we're not expecting them. However, now, for whatever reason,
I'm not seeing the set-config. Thoughts?
> - Dave
/j
- --
Joshua Wise | www.joshuawise.com
GPG Key | 0xEA80E0B3
Quote | <lilo> I akilled [EMAIL PROTECTED] by mistake
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/kLTnPn9tWOqA4LMRAqHFAJ4vaDzt6azK1P+GQb5C3e8WsF04WACgpMjm
h1rbMxxmbcU9DwTQcJD8KcM=
=Wp4l
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
