On Fri, 2010-03-12 at 03:36 -0800, Don Quixote de la Mancha wrote: > On Thu, Mar 11, 2010 at 10:54 AM, Patrick O'Callaghan > <pocallaghan@xxxxxxxxx> wrote: > > It's likely that the disk came with a special driver for Windows, > > whereas the Linux version is using a generic driver. I'd guess the > > answer is probably in the Windows driver code, but of course it will be > > binary and proprietary so it's of no use to anyone. > > There are lots of I/O devices that claim to comply with some published > protocol, but really don't. Some operating systems deal with this by > providing special-case code for particular devices that, while > strictly speaking violate the protocols, at least get the device > working for the user. Many devices provide unique vendor and device > IDs that can be used to know when such workarounds need to be > activated. > > I know that Linux includes such code to support otherwise broken > microprocessors. I don't know whether it also provides support for > broken USB storage devices. > > A specific example is that I can recall a post to one of the FreeBSD > lists which mentioned the addition of a special workaround for the > Kingston USB Flash drives. Interesting. I have a couple of these. Do you have a more specific reference? Google shows a bunch of stuff but nothing that indicates any specific issue with Kingston versus other brands. poc -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
