On Fri, 14 Oct 2005, Conio sandiago wrote: > Hi all, > i have developed a USB host controller driver on MV linux, > Thw controller seems to work correctly, because when i insert a USB > pendrive, The Driver is correctly associated and the Host is able to > read the Device descriptors correctly.
Congratulations! That's not easy to do. > when i run the dmesg command from bash shell, > i see the following messages,does anybody has some idea > usb-storage: scsi cmd done, result=0x0 > usb-storage: *** thread sleeping. > Vendor: Model: USB DISK Pro Rev: 1.1b > Type: Direct-Access ANSI SCSI revision: 00 > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (1:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (2:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (3:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (4:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (5:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (6:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (7:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: device scan complete The Vendor and Model lines come from the SCSI core. They describe your pendriver. The other lines are debugging messages from usb-storage. You can eliminate them by turning off CONFIG_USB_STORAGE_DEBUG. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
