From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] MIPS Support in Release 4
Date: Fri, 28 Jun 2002 03:00:28 -0700 [thread overview]
Message-ID: <8a38124e3039247c81ae888d6c76a8da@collyer.net> (raw)
SGIs are MIPS machines (except perhaps the earliest ones, but the 4Ds
are MIPS). There were ports to one of the SGI Challenge machines and
I believe the Indy or Indigo. I can't recall if these were ever
distributed, and kittens are destroying my office, so I'm not going to
spend the time to find out. Anyway, 4e doesn't include any SGI ports
and SGI never made it easy to get the sort of information (e.g.,
physical memory map, MMU details) that you'd need to port to their
machines, and I think there was quite a bit of variation, though
probably not as much as across Sun's product line, where it seemed
that every new model had a new incompatible MMU. For terminals, the
frame buffers seemed to all be different and incompatible.
next reply other threads:[~2002-06-28 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 10:00 Geoff Collyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-01 12:55 rob pike, esq.
2002-06-28 13:58 rob pike, esq.
2002-07-01 9:45 ` Jim Meier
2002-07-01 9:46 ` Jim Meier
2002-06-28 8:52 Jim Meier
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=8a38124e3039247c81ae888d6c76a8da@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).