Scott Wood wrote: > But you continue to generate v1 EEPROMs. If we get the people who > define the format to accept v2, then we can generate v2 after the fix is > applied, and the (very small) risk of a real CRC failure combined with a > spurious CRC success in the old location would only apply on EEPROMs > which haven't been saved since the update.
Again, I'm confused. Why would we bump the version to v2? What is different in V2 compared to V1? It's highly unlikely that there will ever be a V2. The only reason we went from V0 to V1 is to allow for more than 8 MAC addresses. Now the entire EEPROM is filled with MAC addresses, and so we've reached the hard limit of 31. We would need to switch to a new EEPROM device in order to handle more, and none of the other information in the EEPROM is used by U-Boot. -- Timur Tabi Linux kernel developer at Freescale _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
