An answer and a question: > -----Original Message----- > From: Matthew Dharm [mailto:[EMAIL PROTECTED]] > > Some questions: > (1) I'm guessing that this is an OHCI system, based on your other > messages. Please confirm/deny this. > > (2) Does anyone know why we're not seeing the "OHCI Root Hub" > string in > the output? Did that patch (to identify virtual root hubs) > not make it into the kernel? It's in there but it's not printed unless USB is compiled with CONFIG_USB_DEBUG set. > (3) I'm guessing that the ORB drive had media in it when this > was done. > Please confirm/deny. > > (4) Does this always fail, or just sometimes? It's clear > that at least > one command makes it to the device in this trace -- do others sometime > make it? > > (5) Can you send the logfile processed by syslog with > timestamps? That > can be helpful, especially with timeout/reset conditions. How do you do this? ~Randy > (6) Can you test this on a UHCI system (or OHCI, which ever > you don't have > -- see question 1)? > > (7) I find it somewhat odd that the INQUIRY data returned > happens to be > exactly 255 bytes. It just rubs my instincts funny. Could > you hack the > driver to, in the case of an INQUIRY, only get like 50 bytes? > You should > be able to do this by editing us_transfer_length(). Do that, > retest, and > let me know if it makes a difference. > > The short version is this: Everything seems just fine. But > the device > fails to respond to the status stage of the transfer. The > only thing I > can think to do would be to attempt to reset the device. > That code isn't > done yet, but should get done when I'm back on my feet from surgery. > > Matt Dharm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
