On Wed, 4 May 2005, Grégory SCHMITT wrote: > > > It was natively not working with kernel 2.6.11, so I decided to hack > > > the unusual_devs.h. I added those line: > > > > > > UNUSUAL_DEV(0x0416, 0xc986, 0x0100, 0x0100, > > > "Winbond Electronics Corp.", > > > "CT986", > > > US_SC_DEVICE, > > > US_PR_BULK, > > > NULL, > > > US_FL_IGNORE_RESIDUE | US_FL_FIX_INQUIRY | US_FL_NEED_OVERRIDE), > > > > > > All switches are required, device seems to accept only Bulk according > > > to the Windows driver. > > > > The switches are _not_ all required. Instead of US_PR_BULK you should > > have US_PR_DEVICE, and you should omit US_FL_NEED_OVERRIDE. > > > > Also I doubt that US_FL_FIX_INQUIRY is needed. To justify having it, you > > should post usb-storage verbose debugging logs showing what happens when > > you plug in the device, both with and without the FIX_INQUIRY flag > > present. > > Well, without US_PR_BULK and US_FL_NEED_OVERRIDE, I cannot access the > partition table (fdisk will always fail), so I don't even have access to sda1.
US_FL_NEED_OVERRIDE makes no difference at all to the function of the device. All it does it prevent the driver from writing an informational message in the system log. So you certainly don't need that one. And according to the lsusb information you posted before, the device already reports that it uses the Bulk-only transport so you don't need to specify US_PR_BULK. If you would like to be more helpful, post some usb-storage verbose debugging logs showing what happens when these flags are present and when they are missing. > US_FL_FIX_INQUIRY has proven to be useful to display the vendor & > product information in the dmesg log. Being helpful is very different from being required. Like I said, the flag isn't required. > > It sounds like the ignore-residue-for-writes patch fixed your problem. > > The patch will be included in 2.6.12. The reason for the your slow > > transfers is probably that you are still using the "sync" option. > > I tried to remove the sync option. Data will be corrupted on the key, > even with the patch, though no error messages appear in the log. > Putting a low value (like 16) for max-sectors seems to help, but > transfers are so slow... Please post the usb-storage verbose debugging logs. Without those nobody will be able to help you and your changes won't be accepted. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
