>Methods (b) and (c) should both work. If (b) isn't working, the device >must have crashed it's internal firmware pretty badly.
To true: i have to send the bulk urb's with a timeout, and then do the ugly reset on -ECONNABORT. If i don't set a timeout it hangs forever. No ETIMEDOUT, no EPIPE. BUT: low level control urb's are working (i.e get configuration) - I guess there done in the silicon. I don't quite understand how the hub code interacts with the USB_PORT_FEAT_ENABLE & USB_PORT_FEAT_POWER bit. The hub get status changes via int-urb's, right ? Now what should I do, so that the hub will finds a 'new device' on the port ? (my thought was, that maybe the device is missing some bits out of the init path, and therefor not always getting started after a power of ?) FYI: as far as i could USBSnoop things, there are 3 situations which happen, when you remove the card: 1) The good one: between reads --> Get Device ID give the right info, all ok. 2) During a longer read (i.e. 10 sectors): device fails with shorter transfer, only delivering the read sectors. 3) Somwhere inbetween (before the first sector ?) - device hangs. In case 3 Win2K bluescreens after a while. - sda _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
