Nice to hear you,
try to answer on your questions:
1. sometimes I get the error message when I switch on the board without
connected USB-Device. When I connect an USB-Stick I get all messages which
shown successful communication between platform and stick. 

2. I have two different sort of USB-Sticks to test. Both behave different
during connection but later I can mount then successfully. 
First Stick:
hub 1-0:1.0: connect-debounce failed, port 1 disabled
hub 1-0:1.0: connect-debounce failed, port 1 disabled
usb 1-1: new full speed USB device using isp116x-hcd and address 2
usb 1-1: Product: Mass storage
usb 1-1: Manufacturer: USB
usb 1-1: SerialNumber: D42CB0684156B126
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model: Flash Disk        Rev: 2.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
sda: Unit Not Ready, sense:
: Current: sense key: Unit Attention
    Additional sense: Not ready to ready change, medium may have changed
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=08
sd: Current: sense key: Unit Attention
    Additional sense: Not ready to ready change, medium may have changed
sda: test WP failed, assume Write Enabled
sda: assuming drive cache: write through
sda: Unit Not Ready, sense:
: Current: sense key: Unit Attention
    Additional sense: Not ready to ready change, medium may have changed
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=08
sd: Current: sense key: Unit Attention
    Additional sense: Not ready to ready change, medium may have changed
sda: test WP failed, assume Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 1024000 512-byte hdwr sectors (524 MB)
sda: Write Protect is off
sda: assuming drive cache: write through
 sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0 
-> successful: 
Then my next hands on:
/var # mkdir usbstick
/var # mount -tvfat /dev/sda1 /var/usbstick/
/var # cd usbstick/
/var/usbstick # ls
linux-2.6.12.5  net             security        test
mm              scripts         sound           usr

I am still using LINUX 2.6.12 with your patches for isp116x and changed
isp116x_start() to register usb_root_hub.

Found: 
usb-isp116x-hcd-01.patch
usb-isp116x-hcd-02.patch
            ... 06
at kernel.org. I will check them tomorrow.

With PTD_TRACE and URB_TRACE I can get huge report of td: and <- from and to
the Stick. Within there are blocks with partition tables which are
definitely correct. But depending on the Stick I see more than one cycles of
attemption to collect all information for the SCSI-Subsystem (look above).
Are there any race-condition between USB and SCSI-Subsystem. Untouched
original sticks work best, formatted sticks with XP or LINUX produce
difficulties up to that they are going offline after unsuccessful reset.
Mouse are running OK except that my target has no interface to use it - I
only get the vendor and serial no. nothing else happen. I think interrupt
and bulk transfers running if the first control transfers are successful. 
Delaying command transfers seem to be also interesting for me. 

-----Ursprüngliche Nachricht-----
Von: Olav Kongas [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 17. August 2005 13:22
An: Fukumoto Akira
Cc: linux-usb-devel@lists.sourceforge.net
Betreff: Re: isp1161 with PowerPC



On Wed, 17 Aug 2005, Fukumoto Akira wrote:

> Hello Olav,
> got it to running USB-Stick on my plattform. I have to change to level
> triggered IRQ4. Then I could mount the stick on /dev/sda1. But now I have
a
> different problem when I remove the stick:
>  
> /var # usb 1-1: USB disconnect, address 8
> hub 1-0:1.0: connect-debounce failed, port 1 disabled
> hub 1-0:1.0: connect-debounce failed, port 1 disabled
> hub 1-0:1.0: connect-debounce failed, port 1 disabled
> ......
>  
> It seems to be a non critical error message, but possibly you have an idea
> to find way to avoid it.
> hub_port_connect_change() in /core/hub.c emit the dev_err above.

Can you please enable CONFIG_USB_DEBUG and repost the 
output.

Do you see this error message only when using a specific 
flash drive? Or also for different flash drives? Or also for 
other types of USB devices like mice, keyboards?

Which version of the kernel are you currently using? 
Recently I posted a number of isp patches for 2.6.13-rcX on 
USB list. Are you using any of these patches?

Olav


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to