Re: usbtest test-14 failure: MUSBHDRC + Netchip2280

On Monday 26 March 2007 10:36 am, David Brownell wrote:
> 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?

Oh, and of course -- which version of the musb_hdrc driver are you using.

Ideally you're using the 2.6.21-rc4-omap1 version (current linux-omap GIT)
rather than e.g. some ancient 2.6.10 version ...

In any case, please submit a patch ASAP adding the <asm/arch/hdrc_cnf.h>
header file matching the configuration of that silicon block), so that I
can stop hearing complaints about how the that driver won't even build on
omap2430 ... ;)

- Dave



> 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