[linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Tom Clark
Recently I noticed my NomadII MG mp3 player stopped communicating when plugged in to a uhci controller (using either uhci driver). It looks like the Nomad driver does a bunch of Control-In transfers with zero length data to signal the device. Using uhci, the status transaction of the transfer is

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Greg KH
On Mon, Dec 03, 2001 at 02:16:53PM -0800, Tom Clark wrote: > Recently I noticed my NomadII MG mp3 player stopped communicating when > plugged in to a uhci controller (using either uhci driver). It looks like > the Nomad driver does a bunch of Control-In transfers with zero length data > to signal

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread David Brownell
ot;Tom Clark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 03, 2001 2:16 PM Subject: [linux-usb-devel] UHCI and zero data control transfer > Recently I noticed my NomadII MG mp3 player stopped communicating when > plugged in to a uhci controller (using eit

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Johannes Erdfelt
On Mon, Dec 03, 2001, David Brownell <[EMAIL PROTECTED]> wrote: > I'm not following. If there's really a zero length data IN, the USB > transactions should be (yes?): > > OUT (setup, 8 bytes) This is a SETUP packet BTW. > IN (data, 0 bytes) > OUT (status, 0 bytes). > > Which i

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread David Brownell
> > OUT (setup, 8 bytes) > > This is a SETUP packet BTW. Yes, but I was talking about direction ... see section 8.5.3 of the USB (2.0) spec. It says that if there's no data phase (vs one of zero length, as shown here) the status is an IN ... the status phase is always flagged by a change of

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Johannes Erdfelt
On Mon, Dec 03, 2001, David Brownell <[EMAIL PROTECTED]> wrote: > > > OUT (setup, 8 bytes) > > > > This is a SETUP packet BTW. > > Yes, but I was talking about direction ... see section 8.5.3 of the > USB (2.0) spec. It says that if there's no data phase (vs one of > zero length, as shown h

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Tom Clark
Actually, it's more along the lines of what Johannes outlined. Running the same transfers through a CATC USB Chief, I can see that a successful transfer looks like this : SETUP OUT This looks the exact same way when using a Linux box w/ OHCI and on a Macintosh (OHCI also). Using the Linux UHC

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread David Brownell
> Actually, it's more along the lines of what Johannes outlined. Running the > same transfers through a CATC USB Chief, I can see that a successful > transfer looks like this : > > SETUP > OUT That's what I was hoping didn't happen ... :) > This looks the exact same way when using a Linux box

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-03 Thread Miles Lane
On Mon, 2001-12-03 at 14:46, Greg KH wrote: > On Mon, Dec 03, 2001 at 02:16:53PM -0800, Tom Clark wrote: > > Recently I noticed my NomadII MG mp3 player stopped communicating when > > plugged in to a uhci controller (using either uhci driver). It looks like > > the Nomad driver does a bunch of Co

Re: [linux-usb-devel] UHCI and zero data control transfer

2001-12-07 Thread Tom Clark
on 12/3/01 3:53 PM, David Brownell at [EMAIL PROTECTED] wrote: >> Actually, it's more along the lines of what Johannes outlined. Running the >> same transfers through a CATC USB Chief, I can see that a successful >> transfer looks like this : >> >> SETUP >> OUT > > That's what I was hoping did