On Thu, Apr 06, 2006 at 12:12:04AM +0200, Bernhard Rosenkraenzer wrote:
> Attempting to use a USB 2.0 CF card reader in 2.6.16 and 2.6.16-mm2 (known to
> work back in 2.4 days, unused since) results in this:
Can you enable CONFIG_USB_STORAGE_DEBUG and send the kernel log file to
the linux-usb-dev
Begin forwarded message:
Date: Thu, 6 Apr 2006 00:12:04 +0200
From: Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
To: linux-kernel@vger.kernel.org
Subject: USB 2.0 CF card reader gets reset+offlined immediately with 2.6.16
Attempting to use a USB 2.0 CF card reader in 2.6.16 and 2.6.16-mm2 (known
This is a note to let you know that I've just added the patch titled
Subject: USB: UHCI: don't track suspended ports
to my gregkh-2.6 tree. Its filename is
usb-uhci-don-t-track-suspended-ports.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/
On Wed, 5 Apr 2006, Pete Zaitcev wrote:
> On Wed, 5 Apr 2006 14:16:39 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > > I've put in a printk to check the error code, it's -110, and that is
> > > supposed to be ETIMEDOUT. According to ohci.h, this code is returned
> > > on TD_DEVNOTRESP..
> > The error is caused by a timeout on the USB bus. The device has a limited
> > time (a few microseconds) to respond to a packet; if it doesn't respond in
> > that time you get this error. There's no way to increase the time limit;
> > it's built into the hardware and is part of the USB spec
> > I've put in a printk to check the error code, it's -110, and that is
> > supposed to be ETIMEDOUT. According to ohci.h, this code is returned
> > on TD_DEVNOTRESP.. but now, I'm out of clues.
> There are two main reasons for a device not to respond to a packet: (1)
> the device's firmware has
On Wed, 5 Apr 2006 14:16:39 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> > I've put in a printk to check the error code, it's -110, and that is
> > supposed to be ETIMEDOUT. According to ohci.h, this code is returned
> > on TD_DEVNOTRESP.. but now, I'm out of clues.
> The error is caused
I'm currently looking at developing a way to interface with a couple of
HID devices. Specifically a bill acceptor and a swipe card reader.
Both devices are detected and picked up by the hiddev kernel module, but
as far as I can see the hiddev doesn't provide everything I need to get
full support
On Wed, 5 Apr 2006, Florian Echtler wrote:
> Hello everybody,
>
> I have some USB WLAN device (based on the Atmel AT76C503A) which works
> when connected to a UHCI host controller, but not with an OHCI. I know
> that this would be a question for the driver developer in the first
> place, but the
Hello everybody,
I have some USB WLAN device (based on the Atmel AT76C503A) which works
when connected to a UHCI host controller, but not with an OHCI. I know
that this would be a question for the driver developer in the first
place, but the respective mailing list is long dead, so I tried to fix
> Let me test this patch out. I'm ok with the changes for handling
> both PCI and platform driver. However, I need to take a look at the
> renaming of the fsl driver. The "dr" device supports device and OTG
> modes. I'm concerned about how we distinguish that in the future.
>
> (also, we
On Wed, 5 Apr 2006, Tommi Kyntola wrote:
> (I'm not on the list, so please cc me replies)
>
> IN SHORT:
> I'm experiencing some weird behavior when sending control messages
> to USB endpoints using usb(dev)fs ioctls. Firstly, 2.6 is significantly
> slower than 2.4 (by a factor of 4). Secondly, co
Jarkko Lavinen wrote:
I am trying to get usb mass storage on MMC card working with Windows
on an Arm based test board with 2.6.16-omap1 kernel. Windows detects
the usb mass storage but fails to see the disk.
I load the module with "insmod g_file_storage.ko stall=0
file=/dev/mmcblk0".
When I h
Hi,
Those who have done USB HCD Testing for ehci ,
Please suggest the USB2.0 Card Reader that u have
used , which was successfully tested using usbtest.c.
The card reader should be using a Cypress EX-USB chip.
Please mention the Product Name and if possible the manufacturers.
Please suggest Card
On Wed, 5 Apr 2006, Jarkko Lavinen wrote:
> I am trying to get usb mass storage on MMC card working with Windows
> on an Arm based test board with 2.6.16-omap1 kernel. Windows detects
> the usb mass storage but fails to see the disk.
>
> I load the module with "insmod g_file_storage.ko stall=0
>
On Wednesday 05 April 2006 7:01 am, Ethan Du wrote:
> > >
> > > Do you mean EEM is saving endpoints?
> >
> >No; as I said, it's less demanding because it doesn't need altsettings.
>
> I know the Data Class interface of a networking device shall have a minimum
> of two interface settings. Do you m
Dave:
Thanks a lot for all your explanation. But I still have some questions.
On Monday 03 April 2006 5:32 am, Ethan Du wrote:
>
> > > The only difference is ECM extended a data class
> > > interface. EEM doesn't. Is this the benefit of EEM? And is it more
> > > efficient using less int
I am trying to get usb mass storage on MMC card working with Windows
on an Arm based test board with 2.6.16-omap1 kernel. Windows detects
the usb mass storage but fails to see the disk.
I load the module with "insmod g_file_storage.ko stall=0
file=/dev/mmcblk0".
When I hook the device to Win2K,
(I'm not on the list, so please cc me replies)
IN SHORT:
I'm experiencing some weird behavior when sending control messages
to USB endpoints using usb(dev)fs ioctls. Firstly, 2.6 is significantly
slower than 2.4 (by a factor of 4). Secondly, consecutive calls
appear to further damage the throughp
19 matches
Mail list logo
