All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Lepple <clepple@foo.tho.org>
To: Linux/SGI <linux@cthulhu.engr.sgi.com>
Subject: building an elf64 R10k kernel
Date: Tue, 04 May 1999 03:33:52 +0000	[thread overview]
Message-ID: <372E6AA0.505A6071@foo.tho.org> (raw)

Hey all,
Does anyone out there know any details on building elf64 objects? I was
all happy about seeing Andrew's Indigo2 patches, and decided that I
_had_ to try and make it work on an Indigo2 Impact 10000... Suffice it
to say that it isn't straightforward.

I first tried to get the machine to boot an elf32 kernel. That failed
miserably, since it doesn't recognize 32-bit ELF objects. Comparison of
sashARCS and sash64 indicated that I needed to use elf64. My first
inclination was to just try the same load address as the Indys and r4400
Indigo2s use. I can't remember the exact error message, but the PROM
basically panicked while loading the first word at 0x88002000 (or
wherever). So I tried using the 64 bit start address from sash64 (high
hex nibble is 0xa). Needless to say, the elf32 linker options conflicted
with that one, and the linker (from binutils-2.8.1 or so) seg faulted.

When I finally recompiled with -mips3 and with a revised linker script,
I noticed something curious. Instead of just truncating the 64-bit
addresses, it rounded them off to 0xffffffff. Any thoughts on this? Am I
approaching this wrong?

And does anyone have a semi-offical memory map for the R10k Indigo2s?

-- 
Charles Lepple
System Administrator, Virginia Tech EE Workstation Labs
clepple@ee.vt.edu || http://www.foo.tho.org/charles/

             reply	other threads:[~1999-05-04  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-04  3:33 Charles Lepple [this message]
1999-05-04  3:54 ` building an elf64 R10k kernel Dave Olson
1999-05-04  3:54   ` Dave Olson
1999-05-04 22:16   ` Ralf Baechle
1999-05-04 23:00     ` William J. Earl

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=372E6AA0.505A6071@foo.tho.org \
    --to=clepple@foo.tho.org \
    --cc=linux@cthulhu.engr.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.