Right... sorry about that last message.  I now have my head screwed on
straight.  I was thinking of another babble situation.

As far as I can tell, nothing in my code should ever evoke a babble
situation.  So neither UHCI nor OHCI should be reporting it.

While OHCI reports babble, UHCI does the transfer, but gives garbage data.

If I back out your patch, UHCI works perfectly.  I didn't test OHCI.  I'll
go do that now.

Matt

On Sat, Feb 01, 2003 at 07:24:15PM -0800, David Brownell wrote:
> Matthew Dharm wrote:
> > This gets even more strange...
> > 
> > It looks like transfers that don't use scatter-gather work just fine.
> > INQUIRY, MODE_SENSE, etc. all behave normally.
> > 
> > But, if the transfer is scatter-gather, then somehow the data never makes
> > it in, even tho it's transferred over the wire.
> 
> But you said it reported babbling ... is the issue that UHCI _should_
> have reported such errors like the other drivers, rather than not
> reporting data?
> 
> 
> > I'm only looking at reads now, but this definately used to work just fine.
> 
> I've certainly done storage accesses through OHCI (and EHCI) using sglist
> versions of usb-storage (but not after your latest changes).  That all
> works with no real problems ... format/badblock testing of many gigs, etc.
> But no overruns either.
> 
> - Dave
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

-- 
Matthew Dharm                              Home: [EMAIL PROTECTED] 
Maintainer, Linux USB Mass Storage Driver

You are needink to look more evil.  You likink very strong coffee?
                                        -- Pitr to Dust Puppy
User Friendly, 10/16/1998

Attachment: msg11202/pgp00000.pgp
Description: PGP signature

Reply via email to