From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Make MPC83xx one step closer to full relocation.
Date: Tue, 8 Apr 2008 21:52:52 +0200 [thread overview]
Message-ID: <200804082152.53399.sr@denx.de> (raw)
In-Reply-To: <1207663498.5826.56.camel@gentoo-jocke.transmode.se>
On Tuesday 08 April 2008, Joakim Tjernlund wrote:
> > On 4xx execution always starts at 0xfffffffc (last lword in 32bit address
> > space). This location holds a jump to _start for 405 PPC's and to
> > _start_440 for 440 PPC's. 440 PPC's need some extended initialization
> > (TLB setup etc) and later jump to the 4xx common _start.
>
> OK, then it is like I suspected. What if you rename _start to
> _common_start. Make _start equal _common_start for 405 and rename
> _start_440 to _start, i.e make sure that _start is defined where you
> start executing after the jump.
As I mentioned earlier, _start_440 is mapped to 0xfffff000 via the linker
script since the jump from 0xfffffffc can't be too long (because of the 4k
shadow TLB entry). So renaming _start_440 to _start won't help here. It can
be done, but frankly I don't have the time for it currently.
> > I'm an linker script dyslexic. So no idea if we can handle this solely in
> > the linker script or if we need a new common symbol in the PPC start.S's.
>
> Both ways should be doable I think. A linker script would probably look
> something like(pseudo diff below):
> .text :
> {
> + _monitor_base = . ;
> + PROVIDE (_monitor_base = .);
> cpu/mpc83xx/start.o (.text)
>
> And then add a
> GOT_ENTRY(_monitor_base)
> in start.S
The disadvantage I see is that I need to change the linker scripts for all
boards for such a solution. Doesn't sound like fun.
So for now, I would really like to see the old version with the ugly
CFG_MONITOR_BASE back so that 4xx board can be used again.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-04-08 19:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 14:41 [U-Boot-Users] [PATCH] Make MPC83xx one step closer to full relocation Joakim Tjernlund
2008-03-28 23:33 ` Kim Phillips
2008-03-28 23:47 ` Joakim Tjernlund
2008-03-29 0:01 ` Kim Phillips
2008-03-29 0:04 ` Joakim Tjernlund
2008-04-08 8:58 ` Stefan Roese
2008-04-08 9:31 ` Joakim Tjernlund
2008-04-08 10:06 ` Stefan Roese
2008-04-08 10:50 ` Joakim Tjernlund
2008-04-08 11:58 ` Wolfgang Denk
2008-04-08 13:07 ` Joakim Tjernlund
2008-04-08 13:25 ` Stefan Roese
2008-04-08 14:04 ` Joakim Tjernlund
2008-04-08 19:52 ` Stefan Roese [this message]
2008-04-08 20:30 ` Joakim Tjernlund
2008-04-08 20:41 ` Wolfgang Denk
2008-04-08 20:52 ` Joakim Tjernlund
2008-04-08 21:09 ` Wolfgang Denk
2008-04-08 21:51 ` Joakim Tjernlund
2008-04-08 22:17 ` David Hawkins
2008-04-09 9:40 ` Stefan Roese
2008-04-09 10:44 ` Wolfgang Denk
2008-04-09 11:14 ` Joakim Tjernlund
2008-04-09 11:45 ` Stefan Roese
2008-04-09 12:36 ` Wolfgang Denk
2008-04-08 11:52 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-02-02 19:44 Joakim Tjernlund
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=200804082152.53399.sr@denx.de \
--to=sr@denx.de \
--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