From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ia64 compressed makefile target
Date: Wed, 23 Oct 2002 21:08:14 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805220@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805211@msgid-missing>
>>>>> On Wed, 23 Oct 2002 13:49:35 -0700, Jesse Barnes <jbarnes@sgi.com> said:
Jesse> Elilo 3.1 supports relocation, but now that I look, we're not
Jesse> passing -r to ld when the kernel is linked, which makes me
Jesse> wonder why it works at all.
Hmmh, I may be dense here, but I don't see any code that applies
relocations. I do see code in Elilo that allows loading the kernel at
a non-default address, but not much more than that. Can you clarify?
--david
next prev parent reply other threads:[~2002-10-23 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 3:21 [Linux-ia64] ia64 compressed makefile target Jesse Barnes
2002-10-23 9:26 ` Andreas Schwab
2002-10-23 15:47 ` Jesse Barnes
2002-10-23 17:46 ` Luck, Tony
2002-10-23 19:01 ` David Mosberger
2002-10-23 20:43 ` Luck, Tony
2002-10-23 20:49 ` Jesse Barnes
2002-10-23 20:59 ` Jack Steiner
2002-10-23 21:08 ` David Mosberger [this message]
2002-10-23 21:20 ` Jesse Barnes
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=marc-linux-ia64-105590709805220@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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