From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM
Date: Wed, 20 Aug 2014 12:38:55 -0700 [thread overview]
Message-ID: <53F4F94F.4040700@freescale.com> (raw)
In-Reply-To: <1407918244-1963-1-git-send-email-valentin.longchamp@keymile.com>
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
prev parent reply other threads:[~2014-08-20 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:24 [U-Boot] [PATCH] km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM Valentin Longchamp
2014-07-17 12:47 ` Wolfgang Denk
2014-07-18 9:10 ` Valentin Longchamp
2014-08-12 18:03 ` York Sun
2014-08-13 6:13 ` Valentin Longchamp
2014-08-13 8:24 ` [U-Boot] [PATCH v2] " Valentin Longchamp
2014-08-20 19:38 ` York Sun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F4F94F.4040700@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.