I've turned off all my debug info to see if I see the same symptoms of addressing address 0. Without debug info I can't easily see what's going on, but my USB mouse still initializes fine. So I am assuming I am not seeing this problem. However, I am not using your latest code right now, nor have I been plagued with some of the Chip Select timing problems reported with this driver before.
One thing that might also be different though, is my test sequence: 1) Boot-up board 2) Connect device (USB off) 3) Load usbcore.ko 4) Load ohci-hcd.ko 5) Load input.ko 6) Load usbhid.ko 7) Load usbmouse.ko Maybe if this sequence is different, some module may try to access the device before the address is properly set somewhere. I know in my case everything is nice and orderly (one PTD per interrupt), so I may not be hitting your case. Sorry can't help you further, but you may try this sequence and see if the problem disappears for now (but we'll have to find it before it bites us later). -----Original Message----- From: Olav Kongas [mailto:[EMAIL PROTECTED] Sent: Monday, November 22, 2004 4:01 AM To: Philipp Schmid Cc: [EMAIL PROTECTED]; Lothar Wassmann; Dimitris Lampridis; Michael Subject: [linux-usb-devel] isp116x debug info/timing problem? Hi, I reported some progress with the driver in my last e-mail (can successfully mount/read/write compact flashes inserted in a Trendnet's compact flash reader). But all this only with the debug info on. There is probably a timing problem somewhere so that if the debug info is removed (DPRINTK declared empty), the driver does not work any more. If the DPRINTK is declared empty, the initialization after the device attachment fails as follows. 1. Set-address to 2 (OK) isp116x_pack_ptd_data: MPS=8 FA=0 DIR=0 EP=0 SPD=0 LEN=8 CNT=0 isp116x_pack_ptd_data: f800 0808 0008 0000 --out-> 00 05 02 00 00 00 00 00 isp116x_unpack_ptd_data: MPS=8 FA=0 DIR=0 EP=0 SPD=0 LEN=8 CNT=8 isp116x_unpack_ptd_data: 0408 0808 0008 0000 2. STATUS (OK) isp116x_pack_ptd_data: MPS=8 FA=0 DIR=2 EP=0 SPD=0 LEN=0 CNT=0 isp116x_pack_ptd_data: fc00 0808 0800 0000 isp116x_unpack_ptd_data: MPS=8 FA=0 DIR=2 EP=0 SPD=0 LEN=0 CNT=0 isp116x_unpack_ptd_data: 0000 0808 0800 0000 3. Get first 8 bytes of the device descriptor. Fails, because the transfer is directed to FA=0, while it should be directed to FA=2 by know. If DPRINTK would be defined as a full-blown debug macro, the FA=2 transfer would be made instead and the initialization would continue normally. isp116x_pack_ptd_data: MPS=8 FA=0 DIR=0 EP=0 SPD=0 LEN=8 CNT=0 isp116x_pack_ptd_data: f800 0808 0008 0000 --out-> 80 06 00 01 00 00 08 00 isp116x_unpack_ptd_data: MPS=8 FA=0 DIR=0 EP=0 SPD=0 LEN=8 CNT=0 isp116x_unpack_ptd_data: 5400 0808 0008 0000 usb 1-1: control timeout on ep0in Has anyone of you seen or already solved the above problem? Olav ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
