Re: usbtest test-14 failure: MUSBHDRC + Netchip2280
David Brownell <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Monday 26 March 2007 9:19 am, Alan Stern wrote: > On Mon, 26 Mar 2007, Pandita, Vikram wrote: > > If the MUSBHDRC really did send an extra OUT token, then the bug is in the > MUSBHDRC. If it really sent an IN token but the Netchip set the flag for > an OUT token, then the bug is in the Netchip. Vikram, it would help a lot if you could describe the specific request that's triggering this problem. Read or write? How many bytes of data? Where in the ep0 message does this appear? What does a USB packet sniffer have to say? I've certainly seen silicon issues in both the HDRC and the net2280, so I could believe either one's at fault here. Most of the net2280 issues have workarounds, at least for the main chip versions ... so I'm more suspicious of the HDRC code, since it's been much more of a pain-in-the-butt and is in any case is much newer code. - Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel