> Which version of that driver are you using? As I understand, > the the version that's been in the tree longest didn't work > very well.
Yes, this driver is very borked. We hired a USB company to get it working and to get rid of some USB protocol violations. The driver I'm using is now on the net in http://openzaurus.bkbits.net:8080/buildroot/diffs/packages/kernel-ramses/[EMAIL PROTECTED]|src/.|src/packages/kernel-ramses|hist/packages/kernel-ramses/sl811hs.patch (/me likee longee pathies) The sad thing is that this driver once worked as expected. I haven't changed the underlying kernel since then (linux-2.4.19-rmk7-pxa2). Must be some weird race or variable-not-initialized condition). Therefore I'm seeking for help, even where to put printk's to see what's going on. I am unfortunately absolutely unfluent in USB protocol, TCP/IP is easier than this mess ... > You said there was no device connected -- so the root hub > had no business trying to assign any addresses. It must > have lied to the hub driver about port status. If there's > no device there, of course any attempt to talk to it will > time out ... I thought it was trying to assing a device number to the virtual root hub itself ?!?! Maybe my thought was wrong. I also know that the interrupt status register contained 0x0d: two reserved bits are set and USB-A-Done-Interrupt. The device detect/Resume Interrupt (which would be 0x40) was not set. ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
