From: Ralf Baechle <ralf@uni-koblenz.de>
To: Dave Olson <olson@anchor.engr.sgi.com>,
Charles Lepple <clepple@foo.tho.org>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: building an elf64 R10k kernel
Date: Wed, 5 May 1999 00:16:06 +0200 [thread overview]
Message-ID: <19990505001606.E1063@uni-koblenz.de> (raw)
In-Reply-To: <199905040354.UAA16791@anchor.engr.sgi.com>; from Dave Olson on Mon, May 03, 1999 at 08:54:28PM -0700
On Mon, May 03, 1999 at 08:54:28PM -0700, Dave Olson wrote:
> Charles Lepple wrote:
> | 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.
>
> For r10k Indigo2 to work, you will need to hack the compiler,
> for various reasons (the way the r10k works, plus the fact that
> indigo2 doesn't have i/o cache coherency, interact in some "interesting"
> ways. I would suggest not attempting this port, unless you have a *lot*
> of spare time.
Let me point out that SGI has invented an almost genious workaround for a
R10000 bug that only hits systems without I/O cache coherency, that is the
Indigo2 and O2.
When I first read the description of the bug and it's workaround I thought
I'd be halucinating ...
Ralf
next prev parent reply other threads:[~1999-05-04 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-04 3:33 building an elf64 R10k kernel Charles Lepple
1999-05-04 3:54 ` Dave Olson
1999-05-04 3:54 ` Dave Olson
1999-05-04 22:16 ` Ralf Baechle [this message]
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=19990505001606.E1063@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=clepple@foo.tho.org \
--cc=linux@cthulhu.engr.sgi.com \
--cc=olson@anchor.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.