t;
Sent: Thu, 29 Dec 2005 16:23:38 -0800
Subject: Re: [linux-usb-devel] OHCI Unrecoverable error on ARM Linux 2.6.14
> On Monday 26 December 2005 7:01 pm, Shivahshankar Shankarnarayan Rao wrote:
> > Hi All,
> >
> > Am having a PCI bridge on a custom ARM 922 board. The PCI i
On Monday 26 December 2005 7:01 pm, Shivahshankar Shankarnarayan Rao wrote:
> Hi All,
>
> Am having a PCI bridge on a custom ARM 922 board. The PCI initialization is
> fine and the OHCI driver is called after the Initialization I get "OHCI
> unrecoverable error" and core dumps continuously.
Tho
Hi All,
Am having a PCI bridge on a custom ARM 922 board. The PCI initialization is
fine and the OHCI driver is called after the Initialization I get "OHCI
unrecoverable error" and core dumps continuously.
Looking forward for some pointers and also some links that says why it happens
and how t
Hi all,
I decided to run Snapgear 3.1.1(kernel version
2.4.24-uc0) on Intel GurneyDrive Development
Platform(based on IXP425 processor, USB host
controller is ISP1561).Everything look like normal but
when I plugged into a USB disk I got the following
message:
# hub.c: new USB device 00:04.1-1, ass
On Thu, 25 Mar 2004, David Brownell wrote:
> Guennadi Liakhovetski wrote:
> > Hello
> >
> > I am trying to get CardBus running on a PXA-based system. And as a
> > test-card I am using a USB 2.0 CardBus card. Sometimes it works. Or, at
> > least, inserting a USB device produces an expeced result. B
Guennadi Liakhovetski wrote:
Hello
I am trying to get CardBus running on a PXA-based system. And as a
test-card I am using a USB 2.0 CardBus card. Sometimes it works. Or, at
least, inserting a USB device produces an expeced result. But sometimes I
am getting:
...
err klogd: host/usb-ohci.c: OHCI U
Hello
I am trying to get CardBus running on a PXA-based system. And as a
test-card I am using a USB 2.0 CardBus card. Sometimes it works. Or, at
least, inserting a USB device produces an expeced result. But sometimes I
am getting:
info klogd: cs: cb_alloc(bus 5): vendor 0x1033, device 0x0035
warn
