public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ia64 compressed makefile target
Date: Wed, 23 Oct 2002 20:49:35 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805218@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805211@msgid-missing>

On Wed, Oct 23, 2002 at 12:01:29PM -0700, David Mosberger wrote:
> I don't have a strong preference either way, but I do have some
> concerns about the VMAP_KERNEL.  I really dislike the fact that it
> requires different versions of virtual-to-physical translations for
> kernel addresses.  No other platform does that, so it will be a source
> of continual worry.  Jesse, could you describe your approach a little
> more?  I assume you link the kernel with "ld -r" and have an elilo
> that applies the relocations?

Elilo 3.1 supports relocation, but now that I look, we're not passing -r
to ld when the kernel is linked, which makes me wonder why it works at
all.  But I've confirmed that a kernel stripped with --strip-all doesn't
boot, while the same binary stripped with --strip-debug does (haven't
tried --strip-unneeded, but that should work too).  I can look into it
more if you're not comfortable with the change, and maybe Tony has
something to add?

Thanks,
Jesse


  parent reply	other threads:[~2002-10-23 20:49 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 [this message]
2002-10-23 20:59 ` Jack Steiner
2002-10-23 21:08 ` David Mosberger
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-105590709805218@msgid-missing \
    --to=jbarnes@sgi.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