> > Transcend makes various versions of their SSDs and all begin with TS. You > > can assume that Transcend SSDs with different capacity or format won't > > work too because they likely use the same controller. The naming is this: > > You don't want to assume that because then you will never find out if > there is no problem. I can be certain that no company would be stupid enough to design a separate controller for each capacity and form factor of their devices. They use one or a very few chips. Furthemore, even if they upgrade the chip and produce 64G 2.5" MLC device with the new working chip, you can't tell it from the ID string at all. > > So the problem is that if you match against the full string, you are going > > to miss the other Transcend devices and the patch becomes quite useless. > > Quite the reverse. It's not implausible that only one or two devices are > affected, but match TS SSD is going to match zillions of devices of many > generations for years to come. Thats not good. Why no good? People just get lower performance (on an old motherboard, where no one expects high performance anyway). On the other hand, if you miss a device from the blacklist, people get crashes. Crashes are worse than lower performance. > Experience is also that very few of the existing blacklist entries we > have grow to be large scale wildcards. Mikulas -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
