Re: FTDI driver installation problems

Mike Harrison <mike@xxxxxxxxxxxxxxx> wrote in
news:7ukl91dad0530npakusulihted57av7nij@xxxxxxx:

> It makes life a whole lot easier if you use the eeprom and prorogram a
> product ID (PID) into it (FTDI will allocate you one if you ask
> them). You just need to update the driver .INF files (described in th
> ehelp files of FTDI's MPROG eeprom-programming utility). That way it
> will always look for a driver for your specific PID and ignore any
> previously installed drivers.

That's the plan, and in fact I laid out the board with a spot for the
EEPROM on it. But the documentation (and other comments I googled on this
newsgroup) say that it should work without one. So the idea was to start
with the least number of variables in the equation. <G>

But I may have to install an EEPROM just to see if I can force the driver
to load...
jmk
.

Relevant Pages

  • New max6875 driver may corrupt EEPROMs
    ... driver may cause EEPROM corruptions if used on random systems. ... The EEPROM part of the MAX6875 chip is accessed using rather uncommon ... data write operation, but for a standard EEPROM, this instead means ... system with such a chip would corrupt it as well. ...
    (Linux-Kernel)
  • [PATCH] max6875: new i2c device driver
    ... max6875: new i2c device driver ... +It also provides 512 bytes of user EEPROM. ... the config EEPROM is read into the registers. ... +static struct bin_attribute config_eeprom_attr = { ...
    (Linux-Kernel)
  • Re: Need to access Specific EHCI operational registers
    ... In this eeprom, there are the PCI ... But as some registers exist to ... This driver must be mapping the PCI BAR and access to the standard area ...
    (microsoft.public.development.device.drivers)
  • Re: checksum in (i2c) eeprom driver
    ... >> IMHO the eeprom driver is more of a demonstration driver than one of ... In as much as eeprom is a demonstration driver, ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [bug] e100 bug: checksum mismatch on 82551ER rev10
    ... You should contact the hardware vendor and have the board replaced or upgraded ... with a proper EEPROM. ... Continuing to work with the corrupted EEPROM image that ... I'm afraid that it's not the board that's at fault, it's the driver. ...
    (Linux-Kernel)