From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hardware port
Date: Sat, 29 Jul 2000 12:55:30 -0400 [thread overview]
Message-ID: <200007291656.MAA10280@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 118 bytes --]
I'ld say the mips/carrera port is the easiest to understand.
The magnum one used to be but its not on this release.
[-- Attachment #2: Type: message/rfc822, Size: 1908 bytes --]
From: "James A. Robinson" <jim.robinson@stanford.edu>
To: "Plan 9 Mailing List" <9fans@cse.psu.edu>
Subject: [9fans] hardware port
Date: Fri, 28 Jul 2000 18:06:56 -0700
Message-ID: <200007290106.VAA29898@cse.psu.edu>
I'm wondering which hardware port of Plan 9 was the most straight-forward,
or if there is no such concept? Is there any particular architecture
that is recommended for simplicity or elegance? I gather that it isn't
the i386 PC.
Jim
next reply other threads:[~2000-07-29 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-29 16:55 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-29 1:06 James A. Robinson
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=200007291656.MAA10280@cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--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).