[linux-usb-devel] Re: [bk patch] A cleanup of Paul's 2.5 hiddev update.

2002-07-16 Thread Vojtech Pavlik
On Mon, Jul 15, 2002 at 04:31:38PM -0700, Greg KH wrote: On Sun, Jul 14, 2002 at 08:18:17PM +0200, Vojtech Pavlik wrote: You can import this changeset into BK by piping this whole message to: '| bk receive [path to repository]' or apply the patch as usual.

Re: [linux-usb-devel] USB mouse doesn't work (2.4.19 and 2.5.24)

2002-07-16 Thread shino korah
--- David Brownell [EMAIL PROTECTED] wrote: But the mouse doesn't work. And you know this -- how? I did a cat on /dev/input/mice and moved mice it didn't put any garbage. mouse doesn't work I meant in Xwindows it doesn't move at all. # od -c /dev/input/mice (move

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Matthew Dharm
That's what a clean unlink looks like under EHCI? Okay, then The only reason command_abort() gets called is that the command has been out for over 20 seconds. For that to occur during the data phase (and combined with the 'hang' at the CSW stage) means that the HCD thinks that the device is

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Greg KH
On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote: My -guess- is that the data toggle has been screwed up somewhere. I know this is a problem in the current 2.4 stack, and sometimes in 2.5. Seems to happen when we unlink a urb, and then go to submit it again later. I've seen

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread David Brownell
Matthew Dharm wrote: That's what a clean unlink looks like under EHCI? Okay, then According to the spec for usb_unlink_urb(), that's what an async unlink should look like for *all* host controllers. (Modulo the fact that -ECONNRESET may have different values on different versions of

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread David Brownell
Greg KH wrote: On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote: My -guess- is that the data toggle has been screwed up somewhere. I know this is a problem in the current 2.4 stack, and sometimes in 2.5. UHCI only though, yes? While I wouldn't rule out bugs in OHCI or EHCI,

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Greg KH
On Tue, Jul 16, 2002 at 11:18:22AM -0700, David Brownell wrote: Greg KH wrote: On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote: My -guess- is that the data toggle has been screwed up somewhere. I know this is a problem in the current 2.4 stack, and sometimes in 2.5.

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Matthew Dharm
On Tue, Jul 16, 2002 at 11:11:33AM -0700, David Brownell wrote: Matthew Dharm wrote: That's what a clean unlink looks like under EHCI? Okay, then This particular usb-storage abort problem has been seen before. And is fixed in the 2.5 tree. But it doesn't really address the question of

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Steve Calfee
At 10:33 AM 7/16/02 -0700, Matthew Dharm wrote: That's what a clean unlink looks like under EHCI? Okay, then The only reason command_abort() gets called is that the command has been out for over 20 seconds. For that to occur during the data phase (and combined with the 'hang' at the CSW

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread David Brownell
This particular usb-storage abort problem has been seen before. And is fixed in the 2.5 tree. But it doesn't really address the question of why the command lingered for so long... Not fixed in 2.5.25, fwiw. - Dave --- This sf.net email

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Matthew Dharm
Well, the semantic meaning of STALL really varies among the DWGs. STALL in usb-storage land is a pretty common occurance, actually. It's used to indicate a problem in a single phase of the transaction (which is multiple transfers) and keep synchronization between host and target. Matt On Tue,

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread Steve Calfee
At 01:27 PM 7/16/02 -0700, Matthew Dharm wrote: Well, the semantic meaning of STALL really varies among the DWGs. STALL in usb-storage land is a pretty common occurance, actually. It's used to indicate a problem in a single phase of the transaction (which is multiple transfers) and keep

Re: [linux-usb-devel] Problems with usb-storage

2002-07-16 Thread David Brownell
Matthew Dharm wrote: Well, the semantic meaning of STALL really varies among the DWGs. STALL in usb-storage land is a pretty common occurance, actually. It's used to indicate a problem in a single phase of the transaction (which is multiple transfers) and keep synchronization between host

[linux-usb-devel] debug advice - usb2 + hard drive box

2002-07-16 Thread Steve Pacenka
Good day, I'm testing a USB2 hard drive box under 2.4.19-pre10 with mixed results, mostly lousy. I'm getting hard lockups (keyboard/touchpad nonresponsive, external access to running SSHD futile) in various circumstances which all seem to inhibit logging. So how should I collect debug info to

Re: [linux-usb-devel] debug advice - usb2 + hard drive box

2002-07-16 Thread Randy.Dunlap
On 16 Jul 2002, Steve Pacenka wrote: | Good day, Hi Steve, I don't have debugging hints for you... | http://www.directron.com/usbbox20.html Suggested retail is US$129 !?! but you didn't pay retail for it... [snip] | Or does anyone have a specific USB2 drivebox to recommend? I bought a

Re: [linux-usb-devel] debug advice - usb2 + hard drive box

2002-07-16 Thread Greg KH
On Tue, Jul 16, 2002 at 05:26:59PM -0400, Steve Pacenka wrote: Or does anyone have a specific USB2 drivebox to recommend? I have a ION drive enclosure: http://www.iogear.com/products/product.php?Item=GHE125U and not had any of the problems you are having. greg k-h

Re: [linux-usb-devel] debug advice - usb2 + hard drive box

2002-07-16 Thread David Brownell
Well, one problem with using the cardbus EHCI devices is that for now you need to manually rmmod ehci-hcd before you (a) eject the card, or (b) shut down. (a) is an ehci driver issue, (b) is a cardbus bug, the cardbus code doesn't sequence clean shutdowns correctly. I've got a patch for (a)

[linux-usb-devel] Problems with usb-uhci/esd200 on KT333A

2002-07-16 Thread Stefan Rompf
Hi, [I've already sent this message to linux-usb-users without feedback, but may be this is more a development issue] after updating my computer to a MSI KT3 Ultra board (KT333A chipset), the Archos MP3 jukebox cannot be accessed reliably anymore using Linux. It does not seem to be a hardware