In message 200410192019.31232@brdc01.nexus-tech.net you wrote:
On Tuesday 19 October 2004 06:24 pm, Shannon Holland wrote:
Does anyone have recommendations as to devices that are known to work?
Do these devices fail enumeration? If so, you may want to look at the change going into the kernel. I have several devices that failed on linux that now work.
See:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=109725370016614&w=...
This was marked as open issue on my list. I think we can close it now. It should have been fixed with the latest rework of the USB code in U-Boot, see:
commit 9c998aa83148c75cd734a18958218926313bd54c tree c6d523801214c37337d3995dd1c405a7c329b37d parent f530187dbd69b0534e84b553f9a9803b16ed4999 author Wolfgang Denk wd@castor.denx.de Thu, 21 Jul 2005 11:57:57 +0200 committer Wolfgang Denk wd@castor.denx.de Thu, 21 Jul 2005 11:57:57 +0200
Fix low-level OHCI transfers for ARM920t and MPC5xxx
A new, Windows compatible init sequence was also backported from Linux 2.6, but disabled with #undef NEW_INIT_SEQ as it wouldn't change the behaviour of the memopry sticks we tested. Maybe it's not relevant for mass storage devices. For recerence, see file common/usb.c, function usb_new_device(), section #ifdef NEW_INIT_SEQ.
Feedback appreciated!
Best regards,
Wolfgang Denk