Re: [linux-usb-devel] gadget serial driver -- patch for 2.6

2003-10-08 Thread Al Borchers
Here is a small patch to bk://kernel.bkbits.net/db/linux/gadget-2.6 to fix up the "debug defined but not used error message". Greg KH wrote: > Here's a patch against the latest 2.6 tree that adds the gadget serial > driver. Thanks. > I still think theres some more cleanup that this driver can u

[linux-usb-devel] gadget serial patch for 2.4

2003-10-08 Thread Al Borchers
Dave -- Here is a patch for gadget serial for 2.4 that fixes the wait_cond_interruptible_timeout macro and the "debug defined but not used" warning. This is against bk://kernel.bkbits.net/db/linux/gadget-2.4. Thanks, -- Al# This is a BitKeeper generated patch for the following project: # Project

[linux-usb-devel] Re: usb net2280 driver

2003-10-08 Thread David Brownell
Kallol Biswas wrote: Hello, We have been using net2280 gadget driver for our embedded systems products. It seems net2280 uses only one scatter gather entry. Is there any plan to support more than one scatter gather descriptor? If so how soon. The current driver #defines USE_DMA_CHAINING, which

[linux-usb-devel] usb net2280 driver

2003-10-08 Thread Kallol Biswas
Hello, We have been using net2280 gadget driver for our embedded systems products. It seems net2280 uses only one scatter gather entry. Is there any plan to support more than one scatter gather descriptor? If so how soon. The throughput we got with the existing nett280.c and our gadget printe

[linux-usb-devel] turning off filesystem detection during hotplug

2003-10-08 Thread G. Del Merritt
I have a device that I want to handle specially. While it advertises usb-storage capabilities (and PTP), I do NOT want the kernel (or the hotplug system) to try to mount it as a filesystem. I just want "raw" USB access enabled. More details: I have already tweaked my /etc/hotplug/usb.usermap

Re: [linux-usb-devel] Re: [PATCH 2.6.0-test6] W996[87]CF driver

2003-10-08 Thread Greg KH
On Tue, Oct 07, 2003 at 02:58:14AM +0200, Luca Risolia wrote: > I am really sorry for these inconveniences, but I had a problem with > the mail client (sylpheed 0.9.6), which removes some lines of text > randomly. This patch should be okay now. Let me know. Looks good to me, I've applied it. than

Re: [linux-usb-devel] Re: [PATCH] Lego USB Infrared Tower driverfor 2.6.0-test7

2003-10-08 Thread Greg KH
On Tue, Oct 07, 2003 at 05:21:02PM +0800, David Glance wrote: > good catch - I have updated the patch accordingly Thanks, I've applied this and then cleaned up some formatting issues in the driver (spaces instead of tabs.) And your minor number is 160. I made the change in the driver for that to

[linux-usb-devel] Re: 2.6.0-test6-mm1 uhci-hcd module bugs

2003-10-08 Thread Andreas Schwarz
Andreas Schwarz wrote: > Alan Stern wrote: >> On Thu, 2 Oct 2003, Andreas Schwarz wrote: >> >>> Sometimes when I try to reload the uhci-hcd module (because my USB mouse >>> cursor is stuck (might be a related problem)) I get the following error: The problems disappeared completely after disabling

Re: [linux-usb-devel] If (!usb_reset) then what ???

2003-10-08 Thread Alan Stern
On Wed, 8 Oct 2003, Stavros Markou wrote: > Hi, > > Saying that reset device does not work I mean that there are 2 cases > a) the function returns success without sending anything to the USB BUS > b) the function returns success and all it does is to drive both D+, D- to > zero for 10ms >

Re: [linux-usb-devel] If (!usb_reset) then what ???

2003-10-08 Thread Oliver Neukum
> descriptors the OS should be capable of handling the same device > with different interfaces and more endpoints. > This is the implementation on most OSs and in Linux too in previous kernel > versions 2.4*. Which kernel versions exactly are you observing failures with? Regards

[linux-usb-devel] If (!usb_reset) then what ???

2003-10-08 Thread Stavros Markou
Hi, Saying that reset device does not work I mean that there are 2 cases a) the function returns success without sending anything to the USB BUS b) the function returns success and all it does is to drive both D+, D- to zero for 10ms which is as you know resets the USB BUS However after