Opened 6 years ago

Closed 6 years ago

#11362 closed enhancement (invalid)

Support counterfeit FTDI devices that were bricked by FTDI's Windows driver

Reported by: waddlesplash Owned by: mmlr
Priority: low Milestone: R1
Component: Drivers/USB Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


For what that means, please see: dissasembly of the Windows FTDI driver, attempts by FTDI to get Linux to do the same, and FTDI's response that shows it's intentional.

Looking at Linux's pending patch for this, it appears all we need to do is to add a PID of 0 to the list here.

As to why we should support these "counterfeit" devices:

  • They are extremely widespread (e.g. all Arduinos will be bricked by this)
  • Most consumers have no idea which one is in their device, we shouldn't punish consumers for something done by the manufacturer.

Change History (5)

comment:1 by waddlesplash, 6 years ago

Here's some info on the physical differences:

comment:2 by anevilyak, 6 years ago

Priority: normallow

comment:3 by pulkomandy, 6 years ago

Note that there is no actual bricking, the change is reversible by rewriting the original ID to the EEPROM on the devices. So it is a lot of panic for not much.

Also, not ALL Arduinos will be affected: they stopped using FTDI chips years ago and are using an AVR as a serial to USB adapter. And I doubt real Arduinos are affected (I can't find any official announcement from them at least). Cheap chinese copies probably are, but you get what you paid for with those.

comment:4 by scottmc, 6 years ago

So does Haiku now have support for FTDI chips? If so would it be possible to use for debugging? See #1504

comment:5 by pulkomandy, 6 years ago

Resolution: invalid
Status: newclosed

Yes, we have drivers for most USB serial adapters including FTDI, Prolific, Silicon Labs, and standard USB-CDC. And no, it is not automatically possible to use these in the kernel debugger just because we have drivers. The USB stack isn't fully running when in KDL and we don't want it to be.

Also, why do you add this comment here? This has nothing to do with this ticket.

Finally, I should add that FTDI reverted that update to their drivers and won't be doing this anymore. The driver now only refuses to work with the fake devices but let them continue to work on other systems. Since there is a simple way to fix the "bricked" devices, let's not hack our driver. Closing this ticket.

Note: See TracTickets for help on using tickets.