All of lore.kernel.org
 help / color / mirror / Atom feed
From: olson@anchor.engr.sgi.com (Dave Olson)
To: clepple@foo.tho.org (Charles Lepple)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: building an elf64 R10k kernel
Date: Mon, 3 May 1999 20:54:28 -0700 (PDT)	[thread overview]
Message-ID: <199905040354.UAA16791@anchor.engr.sgi.com> (raw)
In-Reply-To: <372E6AA0.505A6071@foo.tho.org> from Charles Lepple at "May 4, 99 03:33:52 am"

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.

Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

WARNING: multiple messages have this Message-ID (diff)
From: olson@anchor.engr.sgi.com (Dave Olson)
To: Charles Lepple <clepple@foo.tho.org>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: building an elf64 R10k kernel
Date: Mon, 3 May 1999 20:54:28 -0700 (PDT)	[thread overview]
Message-ID: <199905040354.UAA16791@anchor.engr.sgi.com> (raw)
Message-ID: <19990504035428.jscZnPiMq0WRoHM34yMtBp1gVJZHZZPFCDe7z0MUpYQ@z> (raw)
In-Reply-To: <372E6AA0.505A6071@foo.tho.org> from Charles Lepple at "May 4, 99 03:33:52 am"

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.

Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

  reply	other threads:[~1999-05-04  3:56 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 [this message]
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=199905040354.UAA16791@anchor.engr.sgi.com \
    --to=olson@anchor.engr.sgi.com \
    --cc=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.