From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sparc
Date: Mon, 6 Aug 2007 14:59:38 +0100 [thread overview]
Message-ID: <14d4ec18755712820c003fa116ab3ad9@terzarima.net> (raw)
In-Reply-To: <3096bd910708060559i36c92d4bq1a6472e609eb2ca4@mail.gmail.com>
the microsparcs are not the same as the others.
there's a port i did of plan 9 (second edition) to the sparc lx/classic
using fujitsu microsparc documentation (and existing sparc port code).
it's on sources in contrib/forsyth/lx.tgz
you'd need to change it somewhat for the different mmu and screen interfaces,
but otherwise i don't think it would be much work. i can't do it because i got
rid of the microsparcs about ten years ago.
next prev parent reply other threads:[~2007-08-06 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 12:59 Rodolfo (kix)
2007-08-06 13:27 ` Chris Collins
2007-08-06 13:35 ` john
2007-08-06 23:17 ` Geoffrey Avila
2007-08-06 13:59 ` Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-12 14:13 [9fans] sparc Grunditz Mikael - migu
2001-07-12 11:40 Grunditz Mikael - migu
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=14d4ec18755712820c003fa116ab3ad9@terzarima.net \
--to=forsyth@terzarima.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).