On Thu, Oct 23, 2014 at 10:17:03AM +0200, Johan Hovold wrote: > On Thu, Oct 23, 2014 at 04:10:54PM +0800, Greg Kroah-Hartman wrote: > > On Thu, Oct 23, 2014 at 09:58:20AM +0200, Johan Hovold wrote: > > > On Thu, Oct 23, 2014 at 11:39:50AM +0800, Greg Kroah-Hartman wrote: > > > > On Wed, Oct 22, 2014 at 11:31:34PM -0400, Perry Hung wrote: > > > > > An official recent Windows driver from FTDI detects counterfeit devices > > > > > and reprograms the internal EEPROM containing the USB PID to 0, effectively > > > > > bricking the device. > > > > > > How sneaky. > > > > > > Is idProduct the only field that is rewritten? > > > > According to all of the reports I've read, yes, this is what happens, as > > there are api calls to the device that allow anyone to reprogram the > > idProduct field. > > > > > I'm curious about whether the type is still detected "correctly". > > > > What "type" are you referring to? > > We try to detect the type during probe (encoded as an enum > ftdi_chip_type), which is later used when setting the baud rate (but > also affects the packet layout for legacy SIO devices). > > It's done based on bNumInterfaces and bcdDevice. Ah, ok, I don't think those fields can be changed through the api. I could be totally wrong, I'm going to try to dig and find a "clone" device to test it out with, but for now, odds are, this patch should be all that is needed. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
