From: Sascha Hauer <s.hauer@pengutronix.de>
To: Renaud Barbier <renaud.barbier@ge.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/4] ppc: bootm: relocate fdt to valid boot memory
Date: Thu, 5 Sep 2013 14:21:08 +0200 [thread overview]
Message-ID: <20130905122108.GE30069@pengutronix.de> (raw)
In-Reply-To: <1378220067-22296-4-git-send-email-renaud.barbier@ge.com>
Hi Renaud,
On Tue, Sep 03, 2013 at 03:54:26PM +0100, Renaud Barbier wrote:
> For the MPC85xx family of SOCs Linux expects any boot firmware
> information to be passed in the first 64MiB of memory. This adds support
> to ensure that the device tree is relocated to a valid location if it is
> outside that address range.
>
> Signed-off-by: Renaud Barbier <renaud.barbier@ge.com>
> ---
> arch/ppc/include/asm/processor.h | 1 +
> arch/ppc/lib/ppclinux.c | 49 +++++++++++++++++++++++++++++++++++++-
> 2 files changed, 49 insertions(+), 1 deletions(-)
>
> diff --git a/arch/ppc/include/asm/processor.h b/arch/ppc/include/asm/processor.h
> index 04cfb60..6b9b7dd 100644
> --- a/arch/ppc/include/asm/processor.h
> +++ b/arch/ppc/include/asm/processor.h
> @@ -966,6 +966,7 @@ struct cpu_type {
> struct cpu_type *identify_cpu(u32 ver);
>
> #if defined(CONFIG_MPC85xx)
> +#define LINUX_TLB1_MAX_ADDR ((void *)(64 << 20))
I had to drop this patch as it breaks the pcm030 compilation. I have no
idea what the correct value for LINUX_TLB1_MAX_ADDR on MPC5200 is. Can
you send an updated patch?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-09-05 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 14:54 [PATCH v2 0/4] Update P2020RDB board support to allow NFS booting Renaud Barbier
2013-09-03 14:54 ` [PATCH 1/4] of: base: import of_find_node_by_type Renaud Barbier
2013-09-03 14:54 ` [PATCH 2/4] ppc: add and update device tree fixup functions Renaud Barbier
2013-09-03 14:54 ` [PATCH 3/4] ppc: bootm: relocate fdt to valid boot memory Renaud Barbier
2013-09-05 12:21 ` Sascha Hauer [this message]
2013-09-06 10:53 ` Renaud Barbier
2013-09-09 15:08 ` Sascha Hauer
2013-09-03 14:54 ` [PATCH 4/4] ppc: P2020RDB configuration update Renaud Barbier
2013-09-04 6:46 ` [PATCH v2 0/4] Update P2020RDB board support to allow NFS booting Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2013-08-30 13:34 [PATCH " Renaud Barbier
2013-08-30 13:34 ` [PATCH 3/4] ppc: bootm: relocate fdt to valid boot memory Renaud Barbier
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=20130905122108.GE30069@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@ge.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox