From: Zippy <zippy@snappy.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Plan9 on Sun Sparc 5 or RS6000-43P/132 ??
Date: Mon, 21 May 2001 08:39:13 +0000 [thread overview]
Message-ID: <ktsagt0hop58d52963h4ga33cuvf2gc6lq@4ax.com> (raw)
In-Reply-To: <20010515131944.A9A71199E6@mail.cse.psu.edu>
On Tue, 15 May 2001 13:36:07 GMT, forsyth@vitanuova.com wrote:
>if you're working with the sparc 5, which i believe is a microsparc model,
>let me know and i can provide the microsparc side of a port of the old system to the Lx/Classic
>(which was microsparc-based). you'll need to answer The Questions.
>
>the microsparc implementations differ in various ways from the Sparc used in the ss and ss10 ports
>and thus the lx/classic port might provide a more appropriate base for the sparc 5.
>no doubt in practice it is the usual hybrid.
"The Questions", meaning the export questions ?? I am in the US, and
will not export the source or binaries (or anything else, as I have no
place to put it but on my hard disk here in the center of the country)
Sparc5 is uniprocessor like the LX/Classic, so it might work.
Specifically, the hardware I have for this is:
(2) Sparc5's, one 70 MHZ and one 85 MHz (they're exactly the same
except for clock speed, with the TGX framebuffer. Is that framebuffer
supported .. ? Of would I use a PC for a terminal ??
I also have an RS/6000 43P/132 PowerPC machine. It looks like it's
probably not anywhere near supported, though...
--Duane
next prev parent reply other threads:[~2001-05-21 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 13:20 forsyth
2001-05-21 8:39 ` Zippy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-15 8:24 [9fans] " Zippy
2001-05-15 12:29 ` [9fans] " Alexander Povolotsky
2001-05-21 8:38 ` Zippy
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=ktsagt0hop58d52963h4ga33cuvf2gc6lq@4ax.com \
--to=zippy@snappy.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).