Re: [linux-usb-devel] 2.5.2-pre6 OOPS in usb_destroy_configuration

2002-01-05 Thread Peter Osterlund
Johannes Erdfelt <[EMAIL PROTECTED]> writes: > usb-uhci.c looks good as far as reference counting. The core looks > clean. The hub driver looks clean. Atleast in 2.4.13. I should check > 2.5.2-pre6. I don't think this is directly related to my problem, but I think there is a ref counting bug in

Re Re: [linux-usb-devel] USB Query:

2002-01-05 Thread Pankaj Kumar Soni
Hello All I am sending code of that driver. Pankaj. On Thu, 03 Jan 2002 Greg KH wrote : > On Thu, Jan 03, 2002 at 11:09:31AM -, Pankaj Kumar > Soni wrote: > > > > Hello All, > > I have some query regarding USB. > > > > 1.In interrupt mode can i use same end pipe for both >

Re: [linux-usb-devel] 2.5.2-pre6 OOPS in usb_destroy_configuration

2002-01-05 Thread Peter Osterlund
Johannes Erdfelt <[EMAIL PROTECTED]> writes: > On Sat, Jan 05, 2002, Peter Osterlund <[EMAIL PROTECTED]> wrote: > > > > Maybe this is such an unusual situation so that it triggered a > > firmware bug in the drive, causing it to misbehave badly on the bus. > > It definately did get to the discon

Re: [linux-usb-devel] 2.5.2-pre6 OOPS in usb_destroy_configuration

2002-01-05 Thread Johannes Erdfelt
On Sat, Jan 05, 2002, Peter Osterlund <[EMAIL PROTECTED]> wrote: > Johannes Erdfelt <[EMAIL PROTECTED]> writes: > > > On Sat, Jan 05, 2002, Peter Osterlund <[EMAIL PROTECTED]> wrote: > > > > > > Maybe this is such an unusual situation so that it triggered a > > > firmware bug in the drive, causi

Re: [linux-usb-devel] 2.5.2-pre6 OOPS in usb_destroy_configuration

2002-01-05 Thread Peter Osterlund
On Sat, 5 Jan 2002, Johannes Erdfelt wrote: > Random corruption is very rare because of the way USB transfers work. > Typically the entire transfer is aborted and then we don't even try. Unless the drive firmware messed up the data before starting the transfer. But I have no idea how likely that

Re: [linux-usb-devel] 2.5.2-pre6 OOPS in usb_destroy_configuration

2002-01-05 Thread Johannes Erdfelt
On Sat, Jan 05, 2002, Peter Osterlund <[EMAIL PROTECTED]> wrote: > On Sat, 5 Jan 2002, Johannes Erdfelt wrote: > > > Random corruption is very rare because of the way USB transfers work. > > Typically the entire transfer is aborted and then we don't even try. > > Unless the drive firmware messed

[linux-usb-devel] Keyspan USA-19Q PDA Adapter

2002-01-05 Thread David Hampton
Is the Keyspan -19Q model supported in any development or test kernel? I checked my 2.4.17 sources and they only support the -19 and -19W models. The -19Q shows up as vend/prod 0x6cd/0x10b in /var/log/messages. I'm wiling to attempt support, and assume that I should start from the keyspan_pda.c

Re: [linux-usb-devel] Keyspan USA-19Q PDA Adapter

2002-01-05 Thread Greg KH
On Sat, Jan 05, 2002 at 10:24:01AM -0800, David Hampton wrote: > Is the Keyspan -19Q model supported in any development or test kernel? I > checked my 2.4.17 sources and they only support the -19 and -19W > models. The -19Q shows up as vend/prod 0x6cd/0x10b in > /var/log/messages. I'm wiling to

[linux-usb-devel] usb-storage patch to support JMTek USBDrive

2002-01-05 Thread Brian Hall
Submitted for your approval, attached is a patch to support the JMTek USBDrive 2.0 (http://www.usbdrive.com/productinfo.html). The earlier "flashdrive" model is not covered by this, as it is not mass storage compliant. I tested the 32MB model with kernel 2.4.17, and it works fine. Write-prote

[linux-usb-devel] Re: usb-storage patch to support JMTek USBDrive

2002-01-05 Thread Matthew Dharm
Please provide the contents of /proc/bus/usb/devices for reference purposes. Matthew Dharm On Sat, Jan 05, 2002 at 12:39:59PM -0700, Brian Hall wrote: > > Submitted for your approval, attached is a patch to support the JMTek > USBDrive 2.0 (http://www.usbdrive.com/productinfo.html). The earlie

Re: [linux-usb-devel] [PATCH] renaming devrequest typedef

2002-01-05 Thread Greg KH
On Sat, Jan 05, 2002 at 12:10:13AM -0500, Johannes Erdfelt wrote: > > Here ya go. Thanks. I'll merge it with mine (you missed a place devrequest was used, and documentation is always good) and post the merged patch in a day or so when I get the time (relatives visiting over the weekend.) greg

Re: [linux-usb-devel] [PATCH] renaming devrequest typedef

2002-01-05 Thread Johannes Erdfelt
On Sat, Jan 05, 2002, Greg KH <[EMAIL PROTECTED]> wrote: > On Sat, Jan 05, 2002 at 12:10:13AM -0500, Johannes Erdfelt wrote: > > > > Here ya go. > > Thanks. I'll merge it with mine (you missed a place devrequest was > used, and documentation is always good) and post the merged patch in a > day

[linux-usb-devel] Re: usb-storage patch to support JMTek USBDrive

2002-01-05 Thread Brian Hall
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc=104/900 us (12%), #Int= 2, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=e000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=

Re: [linux-usb-devel] [PATCH] renaming devrequest typedef

2002-01-05 Thread Greg KH
On Sat, Jan 05, 2002 at 08:39:48PM -0500, Johannes Erdfelt wrote: > > Cool. Where did I miss the devrequest? arch/cris/drivers/usb-host.c Also, drivers/bluetooth/hci_usb.c needs to be modified now that the field names have changed. Not a big deal, I'll do it. > I seem to recall there being an

Re: [linux-usb-devel] [PATCH] renaming devrequest typedef

2002-01-05 Thread David Brownell
> Hm, I don't remember a change document. David, did you include one in > the existing documentation somewhere? No, but it might be worth creating one. Mostly so folk know what needs doing to update 2.4 drivers. Most of the changes have been adding documentation, but also: there was moving som

Re: [linux-usb-devel] [PATCH] renaming devrequest typedef

2002-01-05 Thread Johannes Erdfelt
On Sat, Jan 05, 2002, David Brownell <[EMAIL PROTECTED]> wrote: > > Hm, I don't remember a change document. David, did you include one in > > the existing documentation somewhere? > > No, but it might be worth creating one. Mostly so folk know what needs > doing to update 2.4 drivers. > > Most