[U-Boot] Errors when starting sandbox
Joe Hershberger
joe.hershberger at ni.com
Mon Oct 1 21:14:48 UTC 2018
Hi Simon,
On Mon, Oct 1, 2018 at 12:32 PM, Simon Glass <sjg at chromium.org> wrote:
> Hi Joe,
>
> When I start sandbox now I see these errors every time. It is possible
> to fix this?
>
> $ u-boot -D
> ...
> Warning: host_lo MAC addresses don't match:
> Address in ROM is ea:06:97:67:f4:b6
> Address in environment is 00:00:11:22:33:44
>
> Warning: host_eth0 MAC addresses don't match:
> Address in ROM is ea:06:97:67:f4:b6
> Address in environment is 00:00:11:22:33:45
>
> Warning: host_enp0s31f6 using MAC address from ROM
>
> Warning: host_eth6 MAC addresses don't match:
> Address in ROM is ea:06:97:67:f4:b6
> Address in environment is 00:00:11:22:33:46
>
> Warning: host_docker_gwbridge using MAC address from ROM
>
> Warning: host_docker0 MAC addresses don't match:
> Address in ROM is ca:07:52:28:25:66
> Address in environment is 00:00:11:22:33:47
>
> Warning: host_veth1f6bcd2 using MAC address from ROM
These are warnings based on commit b96ced9cdb6 (sandbox: eth-raw: Make
random MAC addresses available to eth-raw). Because we don't know the
number of interfaces that exist on the given host when we write the
sandbox.dts, we override the MAC addresses with random ones. In the
normal case (real hardware), we would warn, since the hardware should
know its interfaces.
Do you have a proposed different approach? I don't like the idea of
adding sandbox checks in the core code that prints this warning, and
it also doesn't seem like a great idea to add a hook that doesn't warn
just for sandbox.
I'm happy to work on this, but I didn't address it at the time because
I didn't see a clear way to do it that didn't degrade the code in
order to remove warnings in sandbox.
Cheers,
-Joe
> Regards,
> Simon
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
More information about the U-Boot
mailing list