You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are the kernel, then retrieving the Ethernet MAC address is pretty easy; the binary bootloader passes it to the kernel via ATAGS or command-line (I forget which of those two) or device-tree.
However, if you are U-Boot, then you don't typically receive any of those information sources (well, they're there, but since U-Boot is typically the first code to run on a CPU, or perhaps after just the boot ROM, it would be unprecedented for U-Boot to parse such information). So, if U-Boot wants to use the USB Ethernet controller, how does it determine the MAC address?
I'd rather U-Boot could pull this out of the HW directly, rather than relying on the binary bootloader to pass the information to U-Boot (which in turn would probably depend on the user not breaking config.txt, or even actively configuring it to enable some as-yet-unwritten feature). I assume the MAC must be stored in fuses or similar somewhere, since there doesn't appear to be any non-volatile memory on the RPi board. Either way, can the HW that stores this information please be at least minimally documented? I would hesitate to reverse engineer the binary bootloader; that doesn't seem productive and I'm sure there are all kinds of other issues with that approach.
The text was updated successfully, but these errors were encountered:
If you are the kernel, then retrieving the Ethernet MAC address is pretty easy; the binary bootloader passes it to the kernel via ATAGS or command-line (I forget which of those two) or device-tree.
However, if you are U-Boot, then you don't typically receive any of those information sources (well, they're there, but since U-Boot is typically the first code to run on a CPU, or perhaps after just the boot ROM, it would be unprecedented for U-Boot to parse such information). So, if U-Boot wants to use the USB Ethernet controller, how does it determine the MAC address?
I'd rather U-Boot could pull this out of the HW directly, rather than relying on the binary bootloader to pass the information to U-Boot (which in turn would probably depend on the user not breaking config.txt, or even actively configuring it to enable some as-yet-unwritten feature). I assume the MAC must be stored in fuses or similar somewhere, since there doesn't appear to be any non-volatile memory on the RPi board. Either way, can the HW that stores this information please be at least minimally documented? I would hesitate to reverse engineer the binary bootloader; that doesn't seem productive and I'm sure there are all kinds of other issues with that approach.
The text was updated successfully, but these errors were encountered: