Hi Quentin,
many thanks for all your feedback and input.
> If DM_SEQ_ALIAS is enabled, I believe so.
> I would imagine people be surprised if the same device operates under
two different MAC addresses depending on which SW is running at the
moment (U-Boot or Linux for example).
So far I only found
https://github.com/u-boot/u-boot/blob/master/boot/fdt_support.c#L645-L664,
the fdt_fixup_ethernet() function, which, as far as I can see, is called
after/with boot* commands. Ah, but if U-Boots device tree is used to
boot, then of course it is applied there as well. What I meant is in
bootloader stage before that, when it is about looping through boot
media, and in case network boot options, searching for/executing
boot.scr, in case U-Boot console.
In any case, I will wait for one more opinion/input about this, and are
then happy to try implementing a more generic method: E.g. right into
the above function, generating and directly applying MAC addresses to
aliases which do not have a variable to apply from yet, based on an
existing eth0?addr to start with.
Best regards,
Micha
