9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] power pc port
Date: Mon,  4 Aug 2003 10:31:13 +0100	[thread overview]
Message-ID: <ce157b25547132ee84ecf6d11181a6a7@caldo.demon.co.uk> (raw)
In-Reply-To: <7458b557.0308020816.304c1d0b@posting.google.com>

> AFAIK, SGI isn't publicly available. The last time I tried
> wrestling with SGI about it, they "poltely declined" to
> approve release of the source.

	...

>There's a lot of proprietary hardware inside the older SGIs.
>And I think you'd be hard pressed to find any documentation.

the silly thing is that there are or were linux ports
to several of the SGI devices that ran Plan 9 (and some others). certainly
i've got a copy of such a linux where the files are dated 1998.
if you've got the energy (which i suppose you might
if you've got the incentive of owning the appropriate hardware) you might
find an intelligent human being at SGI who will understand
that if linux exists for it, it is pointless preventing release of Plan 9
source for the same hardware.  unless, of course, they
are particularly astute and are trying to preven the
release of a readable system for that hardware.

alternatively, you could use the Linux code as a guide
to driving the hardware and re-port Plan 9.
it will be hard in the case of l.s and mmu.c because
Linux ever has had, as far as i can tell from arm and powerpc ports,
a remarkably x86-based approach to MMU
handling and Plan 9 takes a quite different approach,
especially on the multiprocessors.

it's a shame because the code in /sys/src/9/power/mmu.c
is a delight: clean multiprocessor mmu handling by wielding
logic (eg, carefully worked out invariants) rather than
sledgehammers (eg, interprocessor traps, locks and signals).
i used a variant on the bebox for that reason.
that code isn't SGIs.  i thought it was a good example to study
in an OS class.



  parent reply	other threads:[~2003-08-04  9:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 15:03 David Presotto
2003-07-29 16:34 ` David Presotto
2003-07-30  8:25   ` plan9
2003-08-01  9:02   ` plan9
2003-08-01 13:39     ` Sape Mullender
2003-08-01 19:43       ` Richard Miller
2003-08-04  8:59         ` plan9
2003-08-04  9:25           ` Charles Forsyth
2003-08-04 14:18           ` ron minnich
2003-08-05 10:22             ` Richard Miller
2003-08-05 12:05               ` northern snowfall
2003-08-05 12:53               ` Dan Cross
2003-08-05 13:19                 ` C H Forsyth
2003-08-05 14:13                 ` northern snowfall
2003-08-05 14:16                   ` northern snowfall
2003-08-06  2:55                 ` boyd, rounin
2003-08-05 13:24               ` andrey mirtchovski
2003-08-05 13:56                 ` Dan Cross
2003-08-05 14:41                   ` Philippe Anel
2003-08-06  1:03                   ` okamoto
2003-08-05 14:31                 ` northern snowfall
2003-08-05 15:25                 ` a
2003-08-06 18:23               ` [9fans] plan9 on Ati Mobility M/M1, HP Omnibook 6000 FODEMESI Gergely
2003-08-01 17:50     ` [9fans] power pc port David Presotto
2003-08-01 18:04       ` Christopher Nielsen
2003-08-04  8:59         ` plan9
2003-08-04  9:26           ` Christopher Nielsen
2003-08-06  9:02             ` plan9
2003-08-04  9:31           ` Charles Forsyth [this message]
2003-08-04 14:19             ` ron minnich
2003-08-04 14:44               ` David Presotto
2003-08-04 14:50                 ` Jack Johnson
2003-08-04 14:42             ` Jack Johnson
2003-08-07 18:06               ` C H Forsyth
2003-08-02  7:44     ` Charles Forsyth

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=ce157b25547132ee84ecf6d11181a6a7@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --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).