Dimitris, Olav Communication would be good. I'm also working on the 1160, but unfortunately, I am working with a 2.6.6 kernel and can't upgrade to 2.6.9 / 2.6.10. This means that I can't easily share code updates with the rest, as it was quite a bit of trouble just getting Lothar's OHCI patch to apply to my tree.
I am currently at a point where I the driver initializes fine, the USB root hub and the number of ports get detected fine and enumeration starts. Thanks to Micheal, Olav, and Lothar's mailings earlier re the FSLargestPacketField, I see the first setup packet coming through and being copied into the buffer, on return the setup packet indicates an error code 5 (TD_DEVNOTRESP - remote device not responding) on two of my devices. On my USB drive I get a NO_ERROR return code and once enumeration completed breaking later on, but that did not seem repeatable. I am digging into what's going on now. I haven't gotten to Olav's earlier posting of configuration packets not getting enough data bytes, yet. Once I get there I will let you know what I find. Is this still an on-going issue? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dimitris Lampridis Sent: Wednesday, November 10, 2004 9:53 AM To: Olav Kongas Cc: Linux USB List Subject: Re: [linux-usb-devel] Re: more on ohci-isp1362 On Wed, 2004-11-10 at 10:06 +0200, Olav Kongas wrote: > With this driver, we see quite a bit of duplicated effort. > Sure we could reduce this by communicating more. So, thanks > for posting this type of info. I try to be more open too. > hi Olav, you're right. We both work on porting the code to 1160, yet there is little communication. I think we should change that asap. I'm very reluctant of posting my code on the list, because I don't want it to spread out, since it is not yet complete, and missing comments etc. But we should exchange opinions and methods to ease our work. So, what is your status? I've currently fixed the Bus Glue part of mine (for a PCI implementation that I use) and I can see in the system log that everything goes smoothly (chip detect, reset, ATL/ITL buffer config), until function hc_start() of ohci-hcd.c gets into messing with the Root Hub. It doesn't seem to set it up correctly. But anyway the real problem comes exactly after that. The subsequent ohci_read_control() call and all the rest IO to come, read D<ffffffff ! Did you see anything similar? -- Dimitris Lampridis <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
