I also am reminded about FTDI's (edit: Windows Update - pushed ) malicious driver/firmware update that bricked the VID/PID of what the driver detected as "counterfeit" FTDI serial to usb transceivers. The resulting change made was to set the VID=0000, PID=0000 thus unbinding the associated drivers from being able to identify the hardware.
Torvalds, within a few days, allowed a kernel patch of usbserial.ko to allow usage from 0000:0000 to rewrite the firmware to fix the devices.
This was an example of a chip company destroying hardware arbitrarily, thus showing another treacherous computing in proprietary software.
Comments
I also am reminded about FTDI's (edit: Windows Update - pushed ) malicious driver/firmware update that bricked the VID/PID of what the driver detected as "counterfeit" FTDI serial to usb transceivers. The resulting change made was to set the VID=0000, PID=0000 thus unbinding the associated drivers from being able to identify the hardware.
Torvalds, within a few days, allowed a kernel patch of usbserial.ko to allow usage from 0000:0000 to rewrite the firmware to fix the devices.
This was an example of a chip company destroying hardware arbitrarily, thus showing another treacherous computing in proprietary software.