From: John W. Linville <linville@tuxdriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] booting elf images where VMA != LMA
Date: Mon, 28 Mar 2005 10:35:56 -0500 [thread overview]
Message-ID: <20050328153553.GB17666@tuxdriver.com> (raw)
In-Reply-To: <6.1.1.1.0.20050325180324.01e61aa0@ptg1.spd.analog.com>
On Fri, Mar 25, 2005 at 06:28:18PM -0500, Robin Getz wrote:
> - if someone is using a old or broken toolchain that does not comply with
> ELF. (which is why I thought of using a config switch).
How old of a toolchain are we contemplating? I wouldn't put a lot
of effort into support crufty old tools...
> - may take a little longer (few cycles) to look in the correct place to get
> the LMA.
I can't imagine this be significant enough to bother with a new
config option...?
Just my $0.02...
John
--
John W. Linville
linville at tuxdriver.com
next prev parent reply other threads:[~2005-03-28 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 23:28 [U-Boot-Users] booting elf images where VMA != LMA Robin Getz
2005-03-28 15:35 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 14:53 Robin Getz
2005-03-25 22:12 ` John W. Linville
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=20050328153553.GB17666@tuxdriver.com \
--to=linville@tuxdriver.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