| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
| |
After further investigation this change is not correct and results in
get_ram_size returning incorrectly large values. Reported first by
Gerlando Falauto.
This reverts commit b8496cced856ff411f1eb2e4eff20f5abe7080b0.
Signed-off-by: Tom Rini <trini@ti.com>
|
|
|
|
|
|
|
| |
The original memory sizing code in get_ram_size clobbers the word
at the base address, but forgets to restore it.
Signed-off-by: Iwo Mergler <Iwo.Mergler@netcommwireless.com>
|
|
|
|
|
|
|
|
|
| |
Checkpatch.pl complains about the volatile qualifier in calls to
get_ram_size(). Remove this qualifier in the prototype and in the
calls where it is useless, and leave it only in the function body
where it is needed.
Signed-off-by: Albert ARIBAUD <albert.u.boot@aribaud.net>
|
|
|
|
|
|
| |
at least on G2 cores.
This fixes get_ram_size() problems on MPC5200 Rev. B boards.
|
|
board-specific files to invoke that common implementation.
|