On Št, 2007-01-04 at 17:07 -0500, Alan Stern wrote:
> On Thu, 4 Jan 2007, Milan Plzik wrote:
>
> > Hello,
> >
> > Sorry for duplicit mail, no one replied to this one, maybe 1st Jan
> > evening wasn't the right date to send something:). I'm also attaching
> > output of lsusb -v after enabling wifi adapter [3].
>
> Probably nobody replied because they didn't have anything worthwhile to
> say.
Sorry then, I did not want to be annoying :(. I apologize.
>
> > Original message follows:
> >
> > I'm trying to fix OHCI driver for one ARM-based device. There is only
> > one device 'hardwired' on the USB bus - atmel USB wifi adapter. The OHCI
> > driver itself loads and initializes itself correctly, but after enabling
> > USB wifi, Attached are both dmesg output [1] and usbmon trace [2] (device
> > was
> > several times turned on and off). The board is running 2.6.19 kernel
> > from handhelds.org tree, but AFAIK, except for the glue code, nothing
> > has been changed. Everything works properly when using WinCE or 2.4
> > kernel, and I believe that the ohci glue and wifi driver do equivalent
> > things in both 2.6 and 2.4 series kernel.
> >
> > OHCI controller itself is only part of one chip on the board.
> >
> > If you have any idea, please, let me know. I'm stuck on this issue for
> > a quite long time, so any advice is welcome:)
> >
> > Milan Plzik
> >
> > [1] dmesg output:
> > <6>samcop usb host samcop usb host: auto-wakeup
> > <7>hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0002
> > <7>samcop usb host samcop usb host: GetStatus roothub.portstatus [0] =
> > 0x00010101 CSC PPS CCS
> > <7>hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
> > <7>hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
> > <7>samcop usb host samcop usb host: GetStatus roothub.portstatus [0] =
> > 0x00100103 PRSC PPS PES CCS
> > <6>usb 1-1: new full speed USB device using samcop usb host and address 2
> > <7>samcop usb host samcop usb host: GetStatus roothub.portstatus [0] =
> > 0x00100103 PRSC PPS PES CCS
> > <3>usb 1-1: device descriptor read/64, error -71
>
> > [2] usbmon trace:
> > c2c98360 180058767 S Ci:000:00 s 80 06 0100 0000 0040 64 <
> > c2c98360 180061035 C Ci:000:00 0 0
> > c2c98360 180061191 S Ci:000:00 s 80 06 0100 0000 0040 64 <
> > c2c98360 180063034 C Ci:000:00 0 0
> > c2c98360 180063180 S Ci:000:00 s 80 06 0100 0000 0040 64 <
> > c2c98360 180065012 C Ci:000:00 0 0
>
> These messages indicate that the ohci-hcd driver thinks the device sent a
> 0-length reply instead of sending its device descriptor. Apparently the
> driver isn't getting the correct packet length.
Thanks, this gives me a point where I can start. But reading USB
protocol specs will be probably neccessary too... .
>
> Alan Stern
>
Milan Plzik
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
