Skip to content
Snippets Groups Projects
Forked from Reform / reform-boundary-uboot
Source project has a limited visibility.
  • Timur Tabi's avatar
    f098c9c8
    fsl: obsolete NXID v0 EEPROMs, automatically upgrade them to NXID v1 · f098c9c8
    Timur Tabi authored
    
    The NXID EEPROM format comes in two versions, v0 and v1.  The only
    difference is in the number of MAC addresses that can be stored.  NXID v0
    supports eight addresses, and NXID v1 supports 23.
    
    Rather than allow a board to choose which version to support, NXID v0 is
    now considered deprecated.  The EEPROM code is updated to support only
    NXID v1, but it can still read EEPROMs formatted with v0.  In these cases,
    the EEPROM data is loaded and the CRC is verified, but the data is stored
    into a v1 data structure.  If the EEPROM data is written back, it is
    written in v1 format.  This allows existing v0-formatted EEPROMs to
    continue providing MAC addresses, but any changes to the data will force
    an upgrade to the v1 format, while retaining all data.
    
    Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
    Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
    f098c9c8
    History
    fsl: obsolete NXID v0 EEPROMs, automatically upgrade them to NXID v1
    Timur Tabi authored
    
    The NXID EEPROM format comes in two versions, v0 and v1.  The only
    difference is in the number of MAC addresses that can be stored.  NXID v0
    supports eight addresses, and NXID v1 supports 23.
    
    Rather than allow a board to choose which version to support, NXID v0 is
    now considered deprecated.  The EEPROM code is updated to support only
    NXID v1, but it can still read EEPROMs formatted with v0.  In these cases,
    the EEPROM data is loaded and the CRC is verified, but the data is stored
    into a v1 data structure.  If the EEPROM data is written back, it is
    written in v1 format.  This allows existing v0-formatted EEPROMs to
    continue providing MAC addresses, but any changes to the data will force
    an upgrade to the v1 format, while retaining all data.
    
    Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
    Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>