What problems do you mean exactly? Maybe it's not that difficult to get
it working with 2.6.17 or newer.
it seems that the UDC model had some changes in 2.6.17 and imx_udc.c wasn't
compiling without some modifications. Let me bring my board back to life and
test again... :-)
Julien
=
[ INFO: possible irq lock inversion dependency detected ]
-
ksoftirqd/0/3 just changed the state of lock:
(ap-xmit_lock){-+..}, at: [f9337224] ppp_async_push+0x2f/0x3b3 [ppp_async]
On Sat, 23 Sep 2006, e.fahle wrote:
Hi,
I wrote a driver for fullspeed device based on the code in usb_skeleton.
Sending data to the device goes through 2 interrupt-endpoints.
So my code uses the fill_int_urb() and submit_urb() and a callback for
writing..
I allow a limited number of
From: Ian Abbott [EMAIL PROTECTED]
Hi,
This patch adds support for three OpenPort ECU data cables from Tactrix
Inc. to the ftdi_sio driver's device ID table. One of the PIDs was
supplied by Donour Sizemore on the ftdi-usb-sio-devel mailing list. The
other two were added by myself after
Hi All,
I am facing some problem with linux ohci driver.
After connect/disconnect of some devices my board gets hang.
By observing the system state it is appearing to me like a deadlock.
Regards,
Rupesh
SysRq : Show State
sibling
task
On Sun 24-09-06 16:49:59, Alexander Gran wrote:
Perhaps your cpu cannot go into deep c states? At least my IBm T40p has that
problem, when USB is enabled.
Yes, and latest -mm's were expected to fix that...
Pavel
regards
Alex
Am
On Mon, 25 Sep 2006, Rupesh Kumar wrote:
Hi All,
I am facing some problem with linux ohci driver.
After connect/disconnect of some devices my board gets hang.
By observing the system state it is appearing to me like a deadlock.
Have you tried this patch?
Am Montag, 25. September 2006 17:07 schrieb Ryan Moszynski:
my last message said that everything worked fine. It did, while I was
at home, where the maximum download speeds I can get are around 16
kbps, however, when I got into town where my speeds average 120 kbps
or so, the device is
This patch (as758) fixes the warn-unused-result messages in dummy-hcd.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
---
Index: usb-2.6/drivers/usb/gadget/dummy_hcd.c
===
--- usb-2.6.orig/drivers/usb/gadget/dummy_hcd.c
+++
here is the info you requested. i got it with my 2.6.15 running as
well as 2.6.18. the dmesg's are different but the lsusb's are the
same.
just a guess, i think that this line from lsusb
##
bMaxPacketSize064
##
should be 2048 for evdo cards, if this is the same as my maxSize
On
This patch (as791) fixes some statement with no effect warnings when
CONFIG_USB_SUSPEND isn't set.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
---
Index: usb-2.6/drivers/usb/core/usb.h
===
--- usb-2.6.orig/drivers/usb/core/usb.h
This patch (as792) fixes ignoring return value warnings in
file_storage.c.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
---
Index: usb-2.6/drivers/usb/gadget/file_storage.c
===
--- usb-2.6.orig/drivers/usb/gadget/file_storage.c
+++
Alan
But if you want to create one anyway, this is how to it.
Edit unusual_devs.h in drivers/usb/storage/ in the kernel
source. Add an entry for the POCKET USB device, with the
appropriate vendor, product and revision numbers, and use the
US_FL_NO_WP_DETECT flag.
I created unusal
On Mon, 25 Sep 2006, Vivek Dharmadhikari wrote:
Alan
But if you want to create one anyway, this is how to it.
Edit unusual_devs.h in drivers/usb/storage/ in the kernel
source. Add an entry for the POCKET USB device, with the
appropriate vendor, product and revision numbers, and
Greg and Andrew:
This series of patches completely reworks the way ohci-hcd carries out
root-hub autosuspends. The existing code is not compatible with the new
core USB autosuspend mechanism.
Patch 1 is a simple one-line change to usbcore with no harmful effects.
It can go directly into
Originally I didn't think any host controller driver would ever use
interrupts and polling at the same time, but it turns out ohci-hcd wants
to do exactly that. This patch (as788) makes it possible.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
---
Index: usb-2.6/drivers/usb/core/hcd.c
The autosuspend technique used by ohci-hcd doesn't mesh well with the
newer USB core autosuspend code. This patch (as789) removes ohci-hcd's
autosuspend support. Now the driver will be usable, but it won't
automatically go into a low-power state when no devices are connected.
That's for a
This patch (as790) adds auto-stop support to ohci-hcd: the driver
will automatically stop the host controller when no devices have been
connected for at least one second. This feature is useful when the
USB core autosuspend facility isn't available, such as when
CONFIG_USB_SUSPEND hasn't been
Hello,
I'm forwarding the mail below on behalf of Marcus Comstedt. I took over
this issue, as I'm currently working on the AmigaOne Linux kernel port.
The developers on the linuxppc-dev mailing list suggested to request a
comment on this issue here first.
Please put Marcus Comstedt and me on CC,
Alan
The driver _did_ enqueue commands after the timeout errors.
Got it ! The USB analyzer indicates that same CBW was repeated three
times in row because the device did not generate ACK for the CBW. After
three failed attempts, usb_stor_Bulk_reset is invoked. Is there a way to
increase the
Hi,
On Monday, 25 September 2006 21:40, Alan Stern wrote:
Greg and Andrew:
This series of patches completely reworks the way ohci-hcd carries out
root-hub autosuspends. The existing code is not compatible with the new
core USB autosuspend mechanism.
Patch 1 is a simple one-line change
On Mon, 25 Sep 2006, Vivek Dharmadhikari wrote:
The driver _did_ enqueue commands after the timeout errors.
Got it ! The USB analyzer indicates that same CBW was repeated three
times in row because the device did not generate ACK for the CBW. After
three failed attempts,
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.18-mm1/drivers/usb/host/ohci-pci.c
linux-2.6.18-mm1/drivers/usb/host/ohci-pci.c
--- linux.vanilla-2.6.18-mm1/drivers/usb/host/ohci-pci.c2006-09-25
The patch for unlimited retries is below. Note this patch is
for 2.6.18; it may need some adjusting to apply to your old kernel.
I am not sure of what sort of adjustment needed to be done on my kernel.
Anyway I applied the patch and I can see that retry count increased to 4
but not infinite
On 9/25/06, Gerhard Pircher [EMAIL PROTECTED] wrote:
1) The EHCI driver uses a structure called echi_qh, which contains
both data to be accessed by the USB hardware through DMA, and
private housekeeping data.
Yes. I am currently tromping through all of this code with steel-toed
boots
This indicates that the problem is a small hardware incompatibility,
as I have said before.
We attached a High Speed hub to our system and inserted this disk in the
hub. The device works perfectly in such mode.
This is more than a small hardware problem. Assuming this HS hub was self
powered,
On 9/23/06, Greg KH [EMAIL PROTECTED] wrote:
Read Documenation/SubmittingPatches for the proper format.
Thank you.
There's at least one bug that turned up just before the weekend that I
want to quash first, then I will update the patchset and post.
Monty
I have a USB webcam with no linux driver G
My windows driver names the device and driver as
CMOS 100K-X Rev 2.01.0025.0 #2
lsusb sees the device as
Bus 001 Device 007: ID 0572:0001 Conexant Systems (Rockwell), Inc. Ezcam II
WebCam
After a google I find no linux drivers for the device. Not
28 matches
Mail list logo
