The static MAC address containing Turing Machines' Vendor OID and your board's unique serial number will be missing. The MAC address should still be unique, as it is with a v2.3/v2.4 board running BMC firmware v2.0.5. There have been posts on GitHub that suggest TM wants to enable the same functionality for TPi v2.3/v2.4 board owners. Having a TM-specific OID will improve network and systems management for customers who will deploy large numbers if TPi v2.5+ boards. Other eeprom fields may prove useful if/when TM gets around to implementing Redfish in the BMC firmware. I suspect TM wants to remove the code that @CFSworks contributed to the firmware to simplify the process and make the firmware image smaller. The BMC has 128MB of on-board memory, and either 128MB (v2.3/v2.4) or 256MB (v2.5.2) of NAND storage.