9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PowerPC Booting
Date: Thu,  3 Jul 2003 17:36:41 -0700	[thread overview]
Message-ID: <06213ce1543aa7b03dd4f1aa74f08302@collyer.net> (raw)
In-Reply-To: <Pine.BSO.4.56.0307041335000.11967@invert.10k.org>

I'm not claiming that it's impossibly hard to port Plan 9 to the Mac
(and I'd be happy to have it running on more common systems, not just
PCs and bitsys), just that it will take some work.

I'd start by looking at a current Darwin release, though I have found
that it takes a while to distill BSD and Linux code, especially
drivers, to their essentials, since they tend to be excessively
complex.  As a recent example, 3ware's Linux driver for their IDE RAID
controller is a 4,174 lines long (3,155 NCSL).  That's over 74 pages,
printed with pr; it's a short book.  This is insane!  It's just a
bloody controller (and the hardware is supposed to be doing most of
the work, as it should).  The entire Unix V6 kernel was only 11,600
lines.  Admittedly, the OpenBSD 3ware driver is just 1,550 lines, but
that's still too big.  It's also true that hardware is even more of a
pain in the ass than it used to be, but over 4,000 lines to drive a
disk controller is just bloat.

As you've alluded, there's also a difference between having Plan 9
running on a particular Mac and having it running on all (or even just
New World) Macs.  For instance, for newer Macs, you'll need USB, USB
keyboard and, for terminals, USB mouse support, unless you can get by
with using the OpenFirmware routines.  I also don't know if the
existing Power PC ports of Plan 9 are prepared to cope with multiple
processors, which isn't fatal, but it would be good to exploit a
second processor on machines that have them.



  reply	other threads:[~2003-07-04  0:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03  5:26 northern snowfall
2003-07-03  4:35 ` Geoff Collyer, geoff
2003-07-03  5:47   ` northern snowfall
2003-07-03  4:50     ` Geoff Collyer, geoff
2003-07-03  5:59       ` northern snowfall
2003-07-03  5:32         ` Tad Hunt
2003-07-03  6:15     ` John Packer, john
2003-07-03 12:15       ` northern snowfall
2003-07-03 12:14         ` Tomas
2003-07-03 16:31           ` Jack Johnson
2003-07-03 13:18     ` D. Brownlee
2003-07-03 14:33       ` northern snowfall
2003-07-03 13:57         ` D. Brownlee
2003-07-03 15:36           ` northern snowfall
2003-07-03 15:23             ` matt
2003-07-04 17:39             ` Jake Luck
2003-07-04  0:36               ` Geoff Collyer, geoff [this message]
2003-07-06 16:52 A. Baker

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=06213ce1543aa7b03dd4f1aa74f08302@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).