public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Remaining CONFIG_NEEDS_MANUAL_RELOC
Date: Sat, 8 Sep 2012 09:15:42 +0200	[thread overview]
Message-ID: <201209080915.42461.marex@denx.de> (raw)
In-Reply-To: <504AEF66.8040601@googlemail.com>

Dear Andreas Bie?mann,

> Dear Marek Vasut,
> 
> On 08.09.12 08:36, Marek Vasut wrote:
> > Hi guys.
> > 
> > I've been pondering if the CONFIG_NEEDS_MANUAL_RELOC is getting away from
> > MIPS/NDS32/AVR32/Sparc/M68K any soon.
> 
> I started playing around with 'elf relocation' for avr32 beginning this
> year when I first saw this dlmalloc relocation warning about aliasing.
> But this is not yet finished and disregarded since then.

Understood.

> > We've been having relocation around for a
> > while, yet these platforms still don't support it. Currently, the
> > MANUAL_RELOC only bloats code all around and usually breaks things that
> > can be nicely cleaned up.
> 
> I see your point.
>
> > So guys, can you please share your roadmaps for this issue?
> 
> I will again look into this later this year. On my roadmap are two major
> things.
>  a) SPL for AT91 to remove the need for AT91bootstrap
>  b) relocation for AVR32
> 
> But sorry, I can not give you a schedule for these features.

Understood, it'd be cool to have the reloc in place really quick, as I'd be able 
to clean up stdio a bit more.

Thanks for your reply Andreas!

> Best regards
> 
> Andreas Bie?mann

Best regards,
Marek Vasut

  reply	other threads:[~2012-09-08  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  6:36 [U-Boot] Remaining CONFIG_NEEDS_MANUAL_RELOC Marek Vasut
2012-09-08  7:10 ` Andreas Bießmann
2012-09-08  7:15   ` Marek Vasut [this message]
2012-09-09 16:16 ` Daniel Schwierzeck
2012-09-09 16:23   ` Marek Vasut

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=201209080915.42461.marex@denx.de \
    --to=marex@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