On Sun, Sep 20, 2020 at 3:57 AM Ansuel Smith <ansuelsmth@xxxxxxxxx> wrote: > > Lots of embedded devices use the mac-address of other interface > extracted from nvmem cells and increments it by one or two. Add two > bindings to integrate this and directly use the right mac-address for > the interface. Some example are some routers that use the gmac > mac-address stored in the art partition and increments it by one for the > wifi. mac-address-increment-byte bindings is used to tell what byte of > the mac-address has to be increased (if not defined the last byte is > increased) and mac-address-increment tells how much the byte decided > early has to be increased. I'm inclined to say if there's a platform specific way to transform MAC addresses, then there should be platform specific code to do that which then stuffs the DT using standard properties. Otherwise, we have a never ending stream of 'generic' properties to try to handle different platforms' cases. Rob
