public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arc: Introduce a possibility to not relocate U-boot
Date: Tue, 20 Feb 2018 17:54:21 +0000	[thread overview]
Message-ID: <1519149260.6393.98.camel@synopsys.com> (raw)
In-Reply-To: <CAPnjgZ3m8bon38Lx8wOFceR9eojV3Nww7hmWGzOFf2jb3Z5eng@mail.gmail.com>

Hi Simon, Tom,

On Sun, 2018-02-04 at 06:40 -0700, Simon Glass wrote:
> On 25 January 2018 at 11:22, Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> > From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> > 
> > Disabling relocation might be useful on ARC for 2 reasons:
> >  a) For advanced debugging with Synopsys proprietary MetaWare debugger
> >     which is capable of accessing much more specific hardware resources
> >     compared to gdb. For example it may show contents of L1 and L2 caches,
> >     internal states of some hardware blocks etc.
> > 
> >     But on the downside MetaWare debugger still cannot work with PIE.
> >     Even though that limitation could be work-arounded with change of ELF's
> >     header and stripping down all debug info but with it we won't have
> >     debug info for source-level debugging which is quite inconvenient.
> > 
> >  b) Some platforms which might benefit from usage of U-Boot basically
> >     don't have enough RAM to accommodate relocation of U-Boot so we
> >     keep code in flash and use as much of RAM as possible for more
> >     interesting things.
> > 
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: Bin Meng <bmeng.cn@gmail.com>
> > Cc: Heiko Schocher <hs@denx.de>
> > Cc: York Sun <york.sun@nxp.com>
> > Cc: Stefan Roese <sr@denx.de>
> > ---
> >  arch/arc/lib/relocate.c | 6 ++++++
> >  arch/arc/lib/start.S    | 8 +++++++-
> >  common/board_f.c        | 3 ++-
> >  3 files changed, 15 insertions(+), 2 deletions(-)
> 
> Reviewed-by: Simon Glass <sjg@chromium.org>

Is it OK if I pull this into my "next" tree?

I'm asking because common/board_f.c is affected even though
that's just an addition of CONFIG_ARC in one #ifdef.

-Alexey

  reply	other threads:[~2018-02-20 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 18:22 [U-Boot] [PATCH] arc: Introduce a possibility to not relocate U-boot Alexey Brodkin
2018-02-04 13:40 ` Simon Glass
2018-02-20 17:54   ` Alexey Brodkin [this message]
2018-02-22 16:18     ` Simon Glass

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=1519149260.6393.98.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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