From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] powerpc/mpc85xx/p1_p2_rdb: add all LAWs during SPL
Date: Fri, 10 Aug 2012 11:05:48 -0500 [thread overview]
Message-ID: <5025315C.8040603@freescale.com> (raw)
In-Reply-To: <110EED8CC96DFC488B7E717A2027A27C11A4E4@039-SN1MPN1-002.039d.mgd.msft.net>
On 08/10/2012 01:54 AM, Huang Changming-R66093 wrote:
> This maybe cause the overlap error:
>
> powerpc-linux-gnu-ld: section .resetvec loaded at
> [00000000ff800ffc,00000000ff800fff] overlaps section .data loaded at
> [00000000ff800ec8,00000000ff80102f]
What tree and toolchain are you using? Did you apply patch 1/2 as well?
Did it build OK for you before these two patches?
> maybe we can think about to remove or modify Kumar's patch:
>
> commit 7639675131673e8f1582d760203a9af34fba9e79
> Author: Kumar Gala <galak@kernel.crashing.org>
> Date: Thu Feb 3 09:02:13 2011 -0600
>
> powerpc/8xxx: Fix LAW init to respect pre-initialized entries
>
> If some pre-boot or earlier stage bootloader (NAND SPL) has setup LAW
> entries consider them good and mark them used.
>
> In the NAND SPL case we skip re-initializing based on the law_table
> since the SPL phase already did that.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Kumar, was this patch to fix a bug (e.g. was one of the LAWs actually in
use at the time?) or just seemed nice?
-Scott
prev parent reply other threads:[~2012-08-10 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 1:03 [U-Boot] [PATCH 1/2] nand/fsl_elbc: shrink SPL a bit by converting out_be32() to __raw_writel() Scott Wood
2012-08-09 1:06 ` [U-Boot] [PATCH 2/2] powerpc/mpc85xx/p1_p2_rdb: add all LAWs during SPL Scott Wood
2012-08-09 2:28 ` McClintock Matthew-B29882
2012-08-09 2:28 ` McClintock Matthew-B29882
2012-08-09 16:52 ` Scott Wood
2012-08-10 6:54 ` Huang Changming-R66093
2012-08-10 16:05 ` Scott Wood [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=5025315C.8040603@freescale.com \
--to=scottwood@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.