On Wednesday 19 December 2007, Alan Stern wrote:
> On Wed, 19 Dec 2007, David Brownell wrote:
>
> > Here's that patch. Please give it at try with USB_DEBUG enabled.
> > Note that the patch has two behavioral changes -- avoid the "what
> > maxpacket should I use?" dance that's not needed, and use a longer
> > delay at one point -- plus a diagnostic change to make EHCI report
> > what control transfers are making trouble.
> >
> > We should at least be able to find out just what calls are making
> > the trouble (and at what point in the sequence), even if the behavior
> > changes don't help. :)
>
> I agree it's worth trying this. For the future, however, I would be
> cautious about removing that "determine maxpacket" code for low- and
> high-speed devices. Windows uses it always, regardless of the device
> speed, and quite likely some devices won't work without it.
I'm trying to understand the failure mode you imply:
<reset>
(a)
Read device descriptor, 64 bytes worth (too big)
--> returns 18 bytes "short" packet
<reset>
(b)
Set address
Read device desriptor, 18 byte worth
--> returns 18 bytes "exact match"
What's removed is the stuff between (a) and (b) right? So if a
device can notice a difference, it's because it goofs the reset.
- Dave
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[Home]
[Video for Linux]
[Photo]
[Yosemite Forum]
[Yosemite Photos]
[Video Projectors]
[PDAs]
[Hacking TiVo]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Devices]
[Big List of Linux Books]
[Free Dating]