[linux-usb-devel] PCI - USB

2005-03-03 Thread Jayaprakash Shanmugam
Hello Everybody, I am working on the PCI-USB card on 2.4. Is there any link that has details of the PCI BIOS fixup routines and the details about PCI resource allocation ? I have ISP 1561 PCI - USB controller on my board (8270 based and running MV Linux 2.4). I was told that the kernel has to

[linux-usb-devel] PCI - USB - Device fails to enumerate. Roothub works.

2005-02-21 Thread Jayaprakash Shanmugam
Hi, I am using ISP 1561 PCI - USB controller in my project (with MVL 3.1). I am able to configure the root hub with ehci-hcd.o. But it is not enumerating when a device is attached (tried with mouse). When no devices are connected, the /proc/usb/devices lists the root hub's configuration. A

Re: [linux-usb-devel] PCI - USB 2.0 on 2.4

2005-01-24 Thread Jayaprakash Shanmugam
Thanks for the inputs Dave. I am insisting on 2.4 kernel was because I am going to use Montavista 3.1 which is 2.4 based. I will give a try on 2.4.29. I tested it on 2.4.20. Thanks Again, Jayaprakash On Fri, 21 Jan 2005 10:25:13 -0800, David Brownell <[EMAIL PROTECTED]> wrote: > On Friday 21

Re: [linux-usb-devel] PCI - USB 2.0 on 2.4

2005-01-21 Thread David Brownell
On Friday 21 January 2005 5:06 am, Jayaprakash Shanmugam wrote: > Hi All, > > I tried a PCI - USB 2.0 card (from D-Link, Ali based Chipset) on my > PC which runs Redhat 9.0 (2.4 kernel). My linux detects the card and > loads the driver. I tried my pen drive with it. It detects the drive > an

[linux-usb-devel] PCI - USB 2.0 on 2.4

2005-01-21 Thread Jayaprakash Shanmugam
Hi All, I tried a PCI - USB 2.0 card (from D-Link, Ali based Chipset) on my PC which runs Redhat 9.0 (2.4 kernel). My linux detects the card and loads the driver. I tried my pen drive with it. It detects the drive and enumerates it. (It says the vendor ID, product ID etc.,) But when I tried

[linux-usb-devel] PCI/USB consustent_alloc assertion violation.

2002-07-09 Thread Pering, Trevor
Hello -- this is a re-post of an earlier problem from last week I'm still working on. I'm using an ARM-based 2.4.18-rmk4 system that is using a USB Bluetooth device to do file transfer. When I transfer a large file, the system hits a "not in interrupt" assertion in consistent_alloc (arch/arm/mm/c