> On the Linux PC, you can try turning on CONFIG_USB_STORAGE_DEBUG or using > usbmon to see what packets are being transferred. Compare that with the > packets being sent by your custom driver and look for differences. > > The Linux driver doesn't include any special commands to enable writes. > > Alan Stern
First of all thanks for your attention to my problem. We had already done that, using usbmon and kernel trace on Linux PC but strangely all packets seem equal. We' ve also try to replicate the same command sequence (including all unnecessary get_descriptors for strings). If you say that no unblocking command is present in Linux driver the thing is still stranger than before... I can't understand why this problem's only with IOmega and not with other HD, the protocol is bulk-only like others and, as I say before, only write command fails on the very first sector and also writing a single sector. We have discovered that using write(10) command and putting to zero into QTD the size of data to be written the command doesn't return error. Looking with usbmon we have also excluded that HD uses write(6) or write(12)... ok... it's a mystery :P Anyway we must go on with other attempts... if you have other suggestions it would be very very appreciated :) Thank you very much, E.Foglio ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
