Dear Kumar Gala,
In message 48A9B08D-9237-4837-91CA-0D23CE1E56D8@kernel.crashing.org you wrote:
The systems I know are the opposite - initially they map more memory than they support, then they determine the real size, then they adjust the mapping to the real size.
Is the point of get_ram_size() to deal with having the same firmware image (binary) be able to be agnostic of memory size?
Yes, this is the key point of it.
I'm not sure I understand what utility one gets out of it if we have SPD eeprom information? I can see some purpose in the soldered memory case if you dont want to tweak binaries between different memory size configs.
With SPD information the benefits go down to the (limited) testing it does, so you might still detect hardware issues - if you try and insert a 2 GiB DIMM and U-Boot sees only 512 MiB then you can be damn sure that something is not working as expected.
Especially on systems where the end user can plug in any types of memory modules that seems to be a pretty useful feature to me.
Best regards,
Wolfgang Denk