Yet another lobsters repost, but a good one. At what point do they just merge with HN?
> I think what’s going on here is if your device pretends to be an FTDI chip, but it doesn’t perfectly emulate it, weird stuff happens when the official FTDI driver doesn’t see something it’s expecting. I’ll leave it to you as the reader to decide whether that’s accidental or intentional on FTDI’s part. Whether it’s accidental or not, I think it’s pretty bad that the driver can crash the system if the device doesn’t respond correctly.
This particularly was a good comment. I guess this is what happens when vendors like FTDI have to fend of an army of chinese clones underselling their IP, introduce a BSOD in windoze driver when the chip isn't perfectly theirs.
> I think what’s going on here is if your device pretends to be an FTDI chip, but it doesn’t perfectly emulate it, weird stuff happens when the official FTDI driver doesn’t see something it’s expecting. I’ll leave it to you as the reader to decide whether that’s accidental or intentional on FTDI’s part. Whether it’s accidental or not, I think it’s pretty bad that the driver can crash the system if the device doesn’t respond correctly.
This particularly was a good comment. I guess this is what happens when vendors like FTDI have to fend of an army of chinese clones underselling their IP, introduce a BSOD in windoze driver when the chip isn't perfectly theirs.