Wolfgang Denk wrote:
What sort of "confusion" do you have? I see two situations: in 99.99% of all cases U-Boot is just a means to boot an OS, and nobody cares a bit about the actual U-Boot output, as long as the OS is runnign after a few seconds, and rather sooner than later.
The confusion stems mostly from the fact that we've been displaying this information for years. If suddenly we stop displaying it, people are going to think that something is wrong. Also, you need to know which U-Boot you're running before you boot the kernel, because the device tree needs to match. No one is going to think to use the 'bdinfo' command to find it.
Many board configurations come in 32-bit and 36-bit versions. E.g.
make P1022DS_config vs. make P1022DS_36BIT_config
The problem is that this isn't standard. "make P1022DS" builds a 32-bit U-Boot. But "make P4080DS" builds a 36-bit U-Boot. So we've been displaying the address map size at boot time in some situations, but not all. My patch makes this standard.
For a few use cases where developers are working on a board, they might wonder which state a board is in - then itis very useful to have a command to display this information any time they are interested in it - even without having to reboot the system.
I agree with adding that information to the bdinfo command. I'm just worried about having it available only there.