All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Make MPC83xx one step closer to full relocation.
Date: Tue, 8 Apr 2008 23:51:15 +0200	[thread overview]
Message-ID: <044c01c899c2$abbb67b0$03323710$@Tjernlund@transmode.se> (raw)
In-Reply-To: <20080408210920.56F3B24842@gemini.denx.de>



> -----Original Message-----
> From: wd at denx.de [mailto:wd at denx.de]
> Sent: den 8 april 2008 23:09
> To: Joakim Tjernlund
> Cc: 'Stefan Roese'; u-boot-users at lists.sourceforge.net; 'Kim Phillips'
> Subject: Re: [U-Boot-Users] [PATCH] Make MPC83xx one step closer to full relocation.
> 
> In message <044901c899ba$83532450$89f96cf0$@Tjernlund@transmode.se> you wrote:
> >
> > > >  .text      :
> > > >   {
> > > > +    _monitor_base = . ;
> > >
> > > There is no guarantee that this is the same as the start address of
> > > .text
> > >
> >
> > I am no link script expert, but I cannot see why that would not be the start
> > of the .text segment?
> 
> There might be other segments at the start of the image...
> 
> See for example cpu/mpc8xx/start.S - while at the  moment  we  really
> start with .text, it would technically be more approrpriate to change
> the  first  256  bytes  (from monitor base to EXC_OFF_SYS_RESET) into
> .rodata or something like this.

Ahh, now I see what you mean and it gave me an idea ...

> 
> > Anyhow, we can go with the other solution instead, define the symbol in start.S
> > instead, if one is needed.
> 
> If it cannot be avoided ;-)

... Stefan, maybe you can #define EXC_OFF_SYS_RESET for 405 to something that
fits with my relocation patch?

  Jocke

  reply	other threads:[~2008-04-08 21:51 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
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 [this message]
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='044c01c899c2$abbb67b0$03323710$@Tjernlund@transmode.se' \
    --to=joakim.tjernlund@transmode.se \
    --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.