Re: [U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM

2014-08-13 Thread Valentin Longchamp
Hi York, On 08/12/2014 08:03 PM, York Sun wrote: On 07/18/2014 02:10 AM, Valentin Longchamp wrote: Hello Wolfgang, On 07/17/2014 02:47 PM, Wolfgang Denk wrote: Dear Valentin, In message 1405599840-11984-1-git-send-email-valentin.longch...@keymile.com you wrote: When u-boot initializes

Re: [U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM

2014-08-12 Thread York Sun
On 07/18/2014 02:10 AM, Valentin Longchamp wrote: Hello Wolfgang, On 07/17/2014 02:47 PM, Wolfgang Denk wrote: Dear Valentin, In message 1405599840-11984-1-git-send-email-valentin.longch...@keymile.com you wrote: When u-boot initializes the RAM (early in boot) it looks for the pram env

Re: [U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM

2014-07-18 Thread Valentin Longchamp
Hello Wolfgang, On 07/17/2014 02:47 PM, Wolfgang Denk wrote: Dear Valentin, In message 1405599840-11984-1-git-send-email-valentin.longch...@keymile.com you 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. At

[U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM

2014-07-17 Thread Valentin Longchamp
When u-boot initializes the RAM (early in boot) it looks for the pram env variable to know which is area it cannot use. At this early boot stage, the pram env variable is not avaible yet since it gets computed in set_km_env that gets called AFTER the RAM initialization. If the pram env variable

Re: [U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM

2014-07-17 Thread Wolfgang Denk
Dear Valentin, In message 1405599840-11984-1-git-send-email-valentin.longch...@keymile.com you 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. At this early boot stage, the pram env variable is not avaible yet