diff options
| author | Timur Tabi <timur@freescale.com> | 2011-02-09 02:00:09 +0000 |
|---|---|---|
| committer | Kumar Gala <galak@kernel.crashing.org> | 2011-04-04 09:24:42 -0500 |
| commit | f098c9c880f08c7b090a4c5bcb924eef1663a32e (patch) | |
| tree | e001991f8f84a9e680a7516ae708af23e7b603ca /board/c2mon/flash.c | |
| parent | c657d898bcf95d5af15f081ed9f03e0ea5b1a16e (diff) | |
| download | u-boot-imx-f098c9c880f08c7b090a4c5bcb924eef1663a32e.zip u-boot-imx-f098c9c880f08c7b090a4c5bcb924eef1663a32e.tar.gz u-boot-imx-f098c9c880f08c7b090a4c5bcb924eef1663a32e.tar.bz2 | |
fsl: obsolete NXID v0 EEPROMs, automatically upgrade them to NXID v1
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: Timur Tabi <timur@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'board/c2mon/flash.c')
0 files changed, 0 insertions, 0 deletions