Re: [PATCH 2/6] USB: serial: ftdi_sio: detect BM chip with iSerialNumber bug

2017-03-08 Thread Ian Abbott
On 02/03/17 14:17, Johan Hovold wrote: On Tue, Feb 28, 2017 at 12:51:24PM +, Ian Abbott wrote: If a BM type chip has iSerialNumber set to 0 in its EEPROM, an incorrect value is read from the bcdDevice field of the USB descriptor, making it look like an AM type chip. Attempt to correct this

Re: [PATCH 2/6] USB: serial: ftdi_sio: detect BM chip with iSerialNumber bug

2017-03-02 Thread Johan Hovold
On Tue, Feb 28, 2017 at 12:51:24PM +, Ian Abbott wrote: > If a BM type chip has iSerialNumber set to 0 in its EEPROM, an incorrect > value is read from the bcdDevice field of the USB descriptor, making it > look like an AM type chip. Attempt to correct this in > ftdi_determine_type() by

[PATCH 2/6] USB: serial: ftdi_sio: detect BM chip with iSerialNumber bug

2017-02-28 Thread Ian Abbott
If a BM type chip has iSerialNumber set to 0 in its EEPROM, an incorrect value is read from the bcdDevice field of the USB descriptor, making it look like an AM type chip. Attempt to correct this in ftdi_determine_type() by attempting to read the latency timer for an AM type chip. If that