Removed from linux-kernel... On tisdagen den 15 juli 2003 20.34, David Brownell wrote: > Roger Larsson wrote: > > I am not alone then... > > > >>hub.c: new USB device 00:02.1-3, assigned address 2 > >>usb_control/bulk_msg: timeout > >>usb-ohci.c: unlink URB timeout > >>usb.c: USB device not accepting new address=2 (error=-110) > > > > This is exactly what I get (2.4.20). But I use quite different hardware. > > STPC Atlas (100MHz, for an embedded project) > > Q: Why doesn't USB work at all? I get "device not accepting address". > > http://www.linux-usb.org/FAQ.html#ts6 > > Basically, if your PCI IRQ routing is broken, USB won't work. Likely > that FAQ entry could stand updating (ACPI vs APCI etc). There are > still significant issues there in 2.6 kernels; and I've hardly ever > seen ACPI do anything except break USB. >
I do get the interrupts! (If I remember correctly we get two) We use TinyBIOS, full control of it - compiled by us. Could you please explain the sequence for getting an accepted address? I guess it is something like this: * Send new address to device * Interrupt when data sent. * --- Wait --- With the possible endings: * Interrupt when new data arrived. * Read result. or * Time out => -110 Alternative endings: * Interrupt when new data arrived. * Read result - nothing there! => timeout error??? (memory IO config problem?) or * Interrupt before data arrived * Read result - nothing there yet => timeout error??? or * Timeout => -110 * Late interrupt, counted but ignored? /RogerL -- Roger Larsson Skellefte� Sweden ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
