Stefan Roese wrote:
Either get the mem
size from there or some flag or version in there can indicate if it's
been "fixed".
I don't think that we have some flag and/or version information in the bd_info
struct. And extending this struct doesn't sound like a good idea to me.
May I suggest an easier way ?
The problem we currently have is some evaluation board(s), we know them,
use wrong DDR configuration parameters, so do as U-Boot does - simply
hardcode memory size for these particular board(s), don't calculate, but
use patched function to calculate memory size for all other boards,
including variety of customers' made. To be absolutely sure, we can
check board revision register - it's theoretically possible that future
board revisions will have more or less memory installed.
This way we can avoid U-Boot to Linux compatibility issues.
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
