Re: [linux-usb-devel] Query over mouting mass-storage driver

On Fri, Apr 28, 2006 at 05:01:32AM +, [EMAIL PROTECTED] wrote: > Hi, > > I have question. > > I have written a Skelton driver for Mass-Storage device (init,exit, probe, > disconnect,release,and open). When I tried to test (by open ("/dev/sda5", > read-only)) my Skelton driver by writing an

[linux-usb-devel] Query over mouting mass-storage driver

Hi, I have question. I have written a Skelton driver for Mass-Storage device (init,exit, probe, disconnect,release,and open). When I tried to test (by open ("/dev/sda5", read-only)) my Skelton driver by writing an application, i failed to open. I noticed that I have to mount the memory stick

[linux-usb-devel] (no subject)

Hi, I have written a Skelton driver for Mass-Storage device (init,exit, probe, disconnect,release,and open). When I tried to test (by open ("/dev/sda5", read-only)) my Skelton driver by writing an application, i failed to open. I noticed that I have to mount the memory stick after doing insmod

Re: [linux-usb-devel] lh7_udc+g_ether vs WinXP

On Thu, Apr 27, 2006 at 02:29:55PM -0700, Marc Singer wrote: > > Let me know of this works better for you when connecting to a Windows > > host using RNDIS. > > > > > > > > I've successfully passed all of the USB tests with this driver. There > w

Re: [linux-usb-devel] lh7_udc+g_ether vs WinXP

> Let me know of this works better for you when connecting to a Windows > host using RNDIS. > > > I've successfully passed all of the USB tests with this driver. There were a couple of buglets as well as a serious logic error. All of the previou

Re: [linux-usb-devel] Is it valid for transfer_flags to change in an URB transaction?

On Thu, 27 Apr 2006, Jamie Guinan wrote: > Hi, > > I'm trying to talk to a Canon PowerShot A520 via libptp, which uses > libusb. The "ptpcam" app works once, then fails after that until I > dis/re-connect the camera. > > open("/proc/bus/usb/001/002", O_RDWR) = 3 > ioctl(3, USBDEVFS_

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

Hi! > > > > During swsusp the system is > > > > supposed to be completely off, with no suspend power available. Hence > > > > all the power sessions are guaranteed to be interrupted, and the boot > > > > kernel doesn't have to worry about destroying any of them. > > > > > > Not ne

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

Hi. On Friday 28 April 2006 05:21, David Brownell wrote: > On Thursday 27 April 2006 9:55 am, Patrick Mochel wrote: > > On Thu, Apr 27, 2006 at 10:34:16AM -0400, Alan Stern wrote: > > > During swsusp the system is > > > supposed to be completely off, with no suspend power available. Hen

[linux-usb-devel] [PATCH 12/12] USB: ftdi_sio: add support for ASK RDR 400 series card reader

From: Ian Abbott <[EMAIL PROTECTED]> This patch adds support for an ASK RDR 400 series contactless card reader to the ftdi_sio driver's device ID table. The product ID was supplied by Adriano Couto on the ftdi-usb-sio-devel list. Signed

[linux-usb-devel] [PATCH 11/12] USB: ftdi_sio: Adds support for iPlus device.

From: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]> Adds support in ftdi_sio usbserial driver for USB modems sold by Plus GSM Company in Poland. Signed-off-by: Luiz Fernando Capitulino <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> --- drivers/usb/serial/ftdi_sio.c

[linux-usb-devel] [PATCH 06/12] USB: net2280: send 0-length packets for ep0

From: Alan Stern <[EMAIL PROTECTED]> This patch (as669) fixes a bug in the net2280 driver. Now it will properly send zero-length packets on ep0 until the control status stage occurs. Signed-off-by: Alan Stern <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> --- driver

[linux-usb-devel] [PATCH 04/12] USB: storage: atmel unusual dev update

From: Olivier Blondeau <[EMAIL PROTECTED]> Originally submitted by Olivier Blondeau <[EMAIL PROTECTED]>, with re-diffing by me. Adds a new atmel unusual_dev entry. Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]> --- drivers/usb/storage/unusual_devs.h |7 +++ 1 files changed, 7 inserti

[linux-usb-devel] [PATCH 08/12] USB: net2280: set driver data before it is used

From: Alan Stern <[EMAIL PROTECTED]> This patch (as671) fixes a bug in the error pathway for the net2280 probe routine. A failure during probe will cause the driver to call pci_get_drvdata before the corresponding pci_set_drvdata has been set. The patch also does a kzalloc conversion. Signed-off

[linux-usb-devel] [PATCH 03/12] USB: Storage: unusual devs update

From: Phil Dibowitz <[EMAIL PROTECTED]> This patch removes the Protocol portion of the Iomega Click! device as it's not needed. Not-needed message reported by Kenneth Crudup <[EMAIL PROTECTED]> Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>

[linux-usb-devel] [PATCH 07/12] USB: net2280: check for shared IRQs

From: Alan Stern <[EMAIL PROTECTED]> This patch (as670) adds a check for whether a shared IRQ was actually generated by the net2280 device. Signed-off-by: Alan Stern <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> --- drivers/usb/gadget/net2280.c |4 1 files

[linux-usb-devel] [PATCH 10/12] USB: ftdi_sio vendor code for RR-CirKits LocoBuffer USB

From: Nathan Bronson <[EMAIL PROTECTED]> This patch adds recognition of the RR-CirKits LocoBuffer USB to the existing FTDI driver. http://www.rr-cirkits.com Signed-off-by: Nathan Bronson <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> --- drivers/usb/serial/ftdi_sio.

[linux-usb-devel] [PATCH 09/12] USB: Use new PCI_CLASS_SERIAL_USB_* defines

From: Jean Delvare <[EMAIL PROTECTED]> We could use the recently added PCI_CLASS_SERIAL_USB_UHCI, PCI_CLASS_SERIAL_USB_OHCI and PCI_CLASS_SERIAL_USB_EHCI defines in more places, for slightly shorter and clearer code. Signed-off-by: Jean Delvare <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartma

[linux-usb-devel] [PATCH 02/12] USB: add new iTegno usb CDMA 1x card support for pl2303

From: Wang Jun <[EMAIL PROTECTED]> Add new iTegno usb CDMA 1x card (usbid '0eba:2080') support to pl2303 driver Signed-off-by: Wang Jun <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> --- drivers/usb/serial/pl2303.c |1 + drivers/usb/serial/pl2303.h |1 + 2 fi

[linux-usb-devel] [PATCH 01/12] USB: Resource leak fix for whiteheat driver

From: Jesper Juhl <[EMAIL PROTECTED]> We may return from drivers/usb/serial/whiteheat.c::whiteheat_attach() without freeing `result' if we leave via the no_firmware: label. Spotted by the coverity checker as #670 Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[

[linux-usb-devel] [PATCH 05/12] USB: net2280: Handle STALLs for 0-length control-IN requests

From: Alan Stern <[EMAIL PROTECTED]> This patch (as668) fixes a typo in net2280. The handler for 0-length control-IN requests should check that the endpoint _isn't_ halted before sending a 0-length packet. Signed-off-by: Alan Stern <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PR

[linux-usb-devel] Is it valid for transfer_flags to change in an URB transaction?

Hi, I'm trying to talk to a Canon PowerShot A520 via libptp, which uses libusb. The "ptpcam" app works once, then fails after that until I dis/re-connect the camera. open("/proc/bus/usb/001/002", O_RDWR) = 3 ioctl(3, USBDEVFS_CLAIMINTERFACE, 0xbe810c64) = 0 ioctl(3, UI_DEV_DESTR

[linux-usb-devel] [GIT PATCH] USB fixes for 2.6.17-rc3

Here are some USB fixes for 2.6.17-rc3. They contain a few small bug fixes and a bunch of new device ids for new devices. All of these changes have been in the -mm tree for a number of weeks. Please pull from: rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/ or if ma

[linux-usb-devel] [PATCH (revised)] usbcore: always turn on hub port power

Greg: Some hubs claim not to support port-power switching, and right now the hub driver believes them and does not enable power to their ports. However it turns out that even though they don't actually switch power, they do ignore all events on a port until told to turn on the power! This pro

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

> > > > But it's not the root cause of the problem either. The same problem > > > > appears if > > > > the device holding the resume partition gets forced into this "broken > > > > suspend" > > > > state. > > > > > > Well, IMO the state may or may not be broken depending on the device, > > > so

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

On Wednesday 26 April 2006 6:22 pm, Patrick Mochel wrote: > On Mon, Apr 24, 2006 at 02:29:51PM -0700, David Brownell wrote: > > > I recently observed this myself and tracked down one problem. The solution > > involves what kexec() does in much the same situation: before starting a > > new kernel

Re: [linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

On Wednesday 26 April 2006 8:32 am, Alan Stern wrote: > I don't know any reason why trying to turn on port power should cause > problems for non-switchable hubs. Can anyone suggest a reason for not > adopting this patch? Lack of a comment about the specific descriptors-are-lying issue you had

Re: [linux-usb-devel] OTG Driver Interrupt Handling

On Tuesday 25 April 2006 3:22 am, rakesh kn wrote: > Hi, > > The OTG driver would consist of 3 kernel modules , > Host driver module, Device driver module, and OTG transceiver driver module. > ... > Should we were to load all three modules at the same time. > Or > Is it t

[linux-usb-devel] Ideazon zboard driver

Hi all, I am struggling with this beast to get it to (fully-)work under linux, this is what I have done: 1. Used usbsnoopy to get some raw zboard usb traffic. 2. Added #debug and #debug_data to hid-core.c 3. modified the xpad driver and I do get the key data but not the special keys, the specia

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

On Thursday 27 April 2006 9:55 am, Patrick Mochel wrote: > On Thu, Apr 27, 2006 at 10:34:16AM -0400, Alan Stern wrote: > > > > During swsusp the system is > > supposed to be completely off, with no suspend power available. Hence all > > the power sessions are guaranteed to be interrup

Re: [linux-usb-devel] why my ep0->queue is alway empty?

On Thursday 27 April 2006 6:41 am, Peter.Chen wrote: > > I have another question: > in eq0_irq routine: > > there are such cases:EP0_IN_DATA_PHASE,and EP0_OUT_DATA_PHASE > (eg.at pxa2xx.udc). Those states are very specific to the pxa25x hardware, and I don't think they match well to any other si

Re: [linux-usb-devel] USB OTG ISR Registration

On Thursday 27 April 2006 1:47 am, Sujith Sankar wrote: > Hi All, > > Our team is implementing a USB OTG Controller Driver in Linux for ARC > controller. The transceiver and OTG controller are integrated. > > We have the following doubt. > > 1.) The implementation involves three modules viz EH

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

On Thu, 27 Apr 2006, Patrick Mochel wrote: > > According to David this shouldn't matter. During swsusp the system is > > supposed to be completely off, with no suspend power available. Hence all > > the power sessions are guaranteed to be interrupted, and the boot kernel > > doesn't have to worr

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

On Thu, Apr 27, 2006 at 10:34:16AM -0400, Alan Stern wrote: > On Thu, 27 Apr 2006, Pavel Machek wrote: > > > Hi! > > > > > The right way to solve this is to make sure that the resuming kernel can > > > correctly determine whether the power session (way back from the original > > > sw-suspend) is

Re: [linux-usb-devel] Queries on Linux USB Sub-system.

On Thu, 27 Apr 2006, Kannan N wrote: > Hi All, > > We are currently using a customized kernel version 2.6.11.10 specific > to our ARM board. > We are testing our USB-OTG controller driver on our board. > We found that, the latest Linux kernel version 2.6.16.11 has added > some features to the

Re: [linux-usb-devel] Queries on Linux USB Sub-system.

On Thu, Apr 27, 2006 at 04:09:10PM +0530, Kannan N wrote: > Hi All, > > We are currently using a customized kernel version 2.6.11.10 specific > to our ARM board. > We are testing our USB-OTG controller driver on our board. > We found that, the latest Linux kernel version 2.6.16.11 has added > s

Re: [linux-usb-devel] USB OTG ISR Registration

On Thu, 27 Apr 2006, Sujith Sankar wrote: > If shared handlers were used, how did you mask the interrupts while servicing? > > If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the > interrupts at the starting, service the received interrupt and unmask > the interrupts before return

Re: [linux-usb-devel] Correct transfer buffer size and struct usb_class_driver questions

On Wed, Apr 26, 2006 at 03:42:33PM -0600, Alisdair Davey wrote: > Secondly I based my driver off the usb_skeleton driver where the name tag in > the usb_class_driver is defined as follows. > > static struct usb_class_driver skel_class = { > .name = "usb/skel%d", > > What is the purpose of

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

On Thu, 27 Apr 2006, Pavel Machek wrote: > Hi! > > > The right way to solve this is to make sure that the resuming kernel can > > correctly determine whether the power session (way back from the original > > sw-suspend) is still intact. It's expected that in many cases it won't > > be, because m

Re: [linux-usb-devel] Correct transfer buffer size and struct usb_class_driver questions

On Wed, 26 Apr 2006, Alisdair Davey wrote: > I have 3 quick questions I hope someone can clarify for me. Development is > being done on Linux Mandrake 10.2 Laptop running kernel 2.6.11-6mddsmp. I can answer your first question but not the others. > First up: I've been using usb_bulk_msg to get d

Re: [linux-usb-devel] why my ep0->queue is alway empty?

Thx dave after invoking fsg->setup,the req is not null. I have another question: in eq0_irq routine: there are such cases:EP0_IN_DATA_PHASE,and EP0_OUT_DATA_PHASE (eg.at pxa2xx.udc).maybe for SET_DESCRIPTOR ,GET_DESCRIPTOR,etc right? and there are USB_REQ_GET_DESCRIPTOR ,USB_REQ_SET_DESCRIPTOR

RE: [linux-usb-devel] USB OTG ISR Registration

>From my point of view, SA_SHIRQ should be ok for the 3 modules. Modules IRQ handler can get the current OTG controller mode. For example, in Host IRQ handler, it will get the mode. If the mode is Host, the handler should deal with the Host mode IRQ event. If the mode is Device, the handler shoul

RE: [linux-usb-devel] USB OTG ISR Registration

No, I didn't use SA_INTERRUPT. I don't see the necessity of masking interrupts. We can use spin_lock to protect critical regions. Best Regards, Leo > -Original Message- > From: Sujith Sankar [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 27, 2006 5:02 PM > To: Li Yang-r58472 > Cc:

[linux-usb-devel] Queries on Linux USB Sub-system.

Hi All, We are currently using a customized kernel version 2.6.11.10 specific to our ARM board. We are testing our USB-OTG controller driver on our board. We found that, the latest Linux kernel version 2.6.16.11 has added some features to the USB Sub-System. Could somebody answer the following

Re: [linux-usb-devel] USB OTG ISR Registration

If shared handlers were used, how did you mask the interrupts while servicing? If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the interrupts at the starting, service the received interrupt and unmask the interrupts before returning? Or were you using SA_SHIRQ | SA_INTERRUPT? If t

RE: [linux-usb-devel] USB OTG ISR Registration

Actually we had done a driver for ARC OTG controller, which is still not very stable. We used shared interrupt handlers. Best Regards, Leo > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sujith > Sankar > Sent: Thursday, April 27, 2006 4:47 PM >

[linux-usb-devel] USB OTG ISR Registration

Hi All, Our team is implementing a USB OTG Controller Driver in Linux for ARC controller. The transceiver and OTG controller are integrated. We have the following doubt. 1.) The implementation involves three modules viz EHCI driver, UDC driver and OTG Controller driver. Shouldn't the ISR's of