I've looked and looked, but I haven't seen anything yet that says this
is intentional, apart from the function name in the disassembly.

It isn't clear if that function name came from the poster or from
debug symbols in the driver.

Relying on that, in a twitter pic, to determine FTDI's actions, seems
a bit of a stretch.

Have FTDI actually said anything?

For otherwise, it looks like a bug, the sort of thing that can happen
if the engineer of the driver isn't permitted to test with the clone
devices.  ;-}

The Linux kernel patch to avoid the problem looks good.  This degrades
the issue to a nuisance for me.

Disclaimer: I'm Scottish by genetics, and so are most of FTDI,
otherwise I've no association with them.

--=20
James Cameron
http://quozl.linux.org.au/
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.