Re: A question for those that know more...
>The driver package released in October 2014 (and subsequently withdrawn) used an operation that would fail on a genuine FTDI device, but was accepted by a counterfeit FTDI device, to reprogram the device's EEPROM with a different USB Product ID (0) which isn't recognised by the FTDI licensed Windows driver.
>Users could fix that up by re-writing a Windows driver .inf file to recognise the changed Product ID. That was the change the Linux kernel driver implemented (an additional Vendor/Product ID pair is recognized).
That is hardly bricking the device, just making your driver no longer talk to the device. Now, I agree that that was the best thing you could do. From the other comment@rds I thought the driver had re-programmed the EEPROM with complete garbage.
As for the fix on Linux, I am pretty sure writing a udev rule would fix that there, as well.
This story reminds me of the PalmOS-iTunes integration, where Palm used the Apple USB id's to "imitate" an ipod.
DISCLAIMER: I am not too much into electronics hacking, not yet, anyway.