From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Remaining CONFIG_NEEDS_MANUAL_RELOC
Date: Sun, 9 Sep 2012 18:23:46 +0200 [thread overview]
Message-ID: <201209091823.46507.marex@denx.de> (raw)
In-Reply-To: <CACUy__XE8Rn8txT+nLuXefi-PYRXKWA_k3AZ4-rWtXuR5iPbfA@mail.gmail.com>
Dear Daniel Schwierzeck,
> Hi Marek,
>
> 2012/9/8 Marek Vasut <marex@denx.de>:
> > Hi guys.
> >
> > I've been pondering if the CONFIG_NEEDS_MANUAL_RELOC is getting away from
> > MIPS/NDS32/AVR32/Sparc/M68K any soon. 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.
> >
> > So guys, can you please share your roadmaps for this issue?
> >
> > Thanks in advance for your reply!
>
> I already have it on my todo list for the next months. Unfortunately I
> can't give you a schedule.
No problem, awesome to know! Thanks!
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-09-09 16:23 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
2012-09-09 16:16 ` Daniel Schwierzeck
2012-09-09 16:23 ` Marek Vasut [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=201209091823.46507.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