From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] qemu-ppce500: Align code at 64k boundary
Date: Mon, 29 Jun 2015 13:38:39 -0500 [thread overview]
Message-ID: <1435603119.9432.33.camel@freescale.com> (raw)
In-Reply-To: <55918BA2.5030106@freescale.com>
On Mon, 2015-06-29 at 11:17 -0700, York Sun wrote:
> Scott,
>
> I lost track on your progress. Please let me know if I should hold this one
> or
> drop it.
>
> York
It shouldn't be needed anymore, as of commit
e1bfd1c6b7bc0dc530247fd9108feba3147adf36 ("powerpc/mpc85xx: Use GOT when
loading IVORs post-relocation").
-Scott
> On 04/22/2015 07:26 PM, Scott Wood wrote:
> > On Wed, 2015-04-22 at 18:13 +0200, Alexander Graf wrote:
> > > The QEMU u-boot located itself at a 4k aligned offset which the rest
> > > of the code didn't really expect. Align it with 64k to allow the memory
> > > code to deal with 64k granularity.
> > >
> > > This fixes broken interrupt delivery with the ppce500 machine for me.
> > >
> > > Signed-off-by: Alexander Graf <agraf@suse.de>
> > > ---
> > > include/configs/qemu-ppce500.h | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/include/configs/qemu-ppce500.h b/include/configs/qemu-
> > > ppce500.h
> > > index 7071849..ec90797 100644
> > > --- a/include/configs/qemu-ppce500.h
> > > +++ b/include/configs/qemu-ppce500.h
> > > @@ -18,7 +18,7 @@
> > > #define CONFIG_QEMU_E500
> > >
> > > #undef CONFIG_SYS_TEXT_BASE
> > > -#define CONFIG_SYS_TEXT_BASE 0xf01000 /* 15 MB */
> > > +#define CONFIG_SYS_TEXT_BASE 0xf10000 /* 15 MB */
> > > #define CONFIG_SYS_GENERIC_BOARD
> > >
> > > #define CONFIG_SYS_MPC85XX_NO_RESETVEC
> >
> > I think we have a similar problem with NAND, SD, etc. boot on some
> > targets. I'll try to fix it so that the existing addresses work.
> >
> > -Scott
> >
> >
prev parent reply other threads:[~2015-06-29 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:13 [U-Boot] [PATCH] qemu-ppce500: Align code at 64k boundary Alexander Graf
2015-04-23 2:26 ` Scott Wood
2015-06-29 18:17 ` York Sun
2015-06-29 18:38 ` 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=1435603119.9432.33.camel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox