On Thursday 05 August 2004 06:13, Ian Molton wrote: > I now can get interrupts frmo the device, so its *nearly* there.
You forgot the smiley face. :) > My one problem is that Im chainbooting from winCE so I cant be sure the > controller hasnt been futzed with. > > The obvious problem to attack is this one: That is, the first thing that obviously went wrong (in your dmesg)... > e7xx-ohci e7xx-ohci0: urb c02f8d98 path 1 ep0out 5ec20000 cc 5 --> > status -110 This is your very first USB transfer, a SET_ADDRESS... Do you know if this is the SETUP or the IN packet that's not working? OHCI has a VERBOSE mode that'll dump that info. Do you know what the device sees? In particular, if the device received its address, that'd indicate that (a) the TD for the SETUP packet was read, (b) the data for that packet was also read, (c) data signaling is working (differential d+/d-) rather than just sensing the D+ pullup. (I'm assuming the RESET on that root hub port really did work correctly.) Likewise, if it doesn't see its address, then at least one of those things is broken ... :) - Dave ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
