20 Aug
2014
20 Aug
'14
9:38 p.m.
On 08/13/2014 01:24 AM, Valentin Longchamp wrote:
When u-boot initializes the RAM (early in boot) it looks for the "pram" env variable to know which is area it cannot use. If the "pram" env variable is not found, the default CONFIG_PRAM value is used.
This value used to be 0 (no protection at all). This patch sets it to a value that covers PHRAM and PNVRAM that must be protected in our case.
Signed-off-by: Valentin Longchamp valentin.longchamp@keymile.com Signed-off-by: Holger Brunck holger.brunck@keymile.com
Changes in v2:
- simplify the commit message for more clarity.
Applied to u-boot-mpc85xx master branch, awaiting for upstream.
York