From: "Kevin D. Kissell" <kevink@mips.com>
To: "Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>,
"Kaj-Michael Lang" <milang@tal.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: Linux on a Tektronix XP217C xterm
Date: Tue, 8 May 2001 10:50:37 +0200 [thread overview]
Message-ID: <001701c0d79b$f9f10980$0deca8c0@Ulysses> (raw)
In-Reply-To: Pine.GSO.4.10.10105080959500.13343-100000@escobaria.sonytel.be
> On Tue, 8 May 2001, Kaj-Michael Lang wrote:
> > Any chance of getting linux running on a tektronix x-terminal ? It has
> > a LR33020 cpu, that I think is a R3000 integrated with some graphics
> > chip. I've tried searching for documentation for the chip but I didn't
> > find anything.
>
> IIRC there's a different separate graphics chip in the 217. I think the
33020
> is not a MIPS, but a RISC chip from LSI Logic.
The 33xx0 family are MIPS-compatible designs that were done
in-house at LSI logic. At the level of the user-mode instruction
set, they are compatible with MIPS-I/R3000 - indeed, the basic
pipeline looks like it was taken directly from the R3000. But the
system coprocessor was radically modified and simplified and in
particular there is no TLB/MMU. Standard Linux therefore won't fly
on it, though some variant of uClinux might.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Kaj-Michael Lang <milang@tal.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Linux on a Tektronix XP217C xterm
Date: Tue, 8 May 2001 10:50:37 +0200 [thread overview]
Message-ID: <001701c0d79b$f9f10980$0deca8c0@Ulysses> (raw)
Message-ID: <20010508085037.P0kMGrU4oi7eNSfeC0LDXG4yWPScBYu3SVvvUMpxzi4@z> (raw)
In-Reply-To: Pine.GSO.4.10.10105080959500.13343-100000@escobaria.sonytel.be
> On Tue, 8 May 2001, Kaj-Michael Lang wrote:
> > Any chance of getting linux running on a tektronix x-terminal ? It has
> > a LR33020 cpu, that I think is a R3000 integrated with some graphics
> > chip. I've tried searching for documentation for the chip but I didn't
> > find anything.
>
> IIRC there's a different separate graphics chip in the 217. I think the
33020
> is not a MIPS, but a RISC chip from LSI Logic.
The 33xx0 family are MIPS-compatible designs that were done
in-house at LSI logic. At the level of the user-mode instruction
set, they are compatible with MIPS-I/R3000 - indeed, the basic
pipeline looks like it was taken directly from the R3000. But the
system coprocessor was radically modified and simplified and in
particular there is no TLB/MMU. Standard Linux therefore won't fly
on it, though some variant of uClinux might.
Regards,
Kevin K.
next prev parent reply other threads:[~2001-05-08 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 6:56 Linux on a Tektronix XP217C xterm Kaj-Michael Lang
2001-05-08 6:56 ` Kaj-Michael Lang
2001-05-08 7:59 ` Mike Barnes
2001-05-08 19:21 ` Alan Olsen
2001-05-08 8:00 ` Geert Uytterhoeven
2001-05-08 8:24 ` Kaj-Michael Lang
2001-05-08 8:24 ` Kaj-Michael Lang
2001-05-08 8:50 ` Kevin D. Kissell [this message]
2001-05-08 8:50 ` Kevin D. Kissell
2001-05-08 19:51 ` Ralf Baechle
2001-05-08 13:07 ` Alan Cox
2001-05-08 13:07 ` Alan Cox
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='001701c0d79b$f9f10980$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-mips@oss.sgi.com \
--cc=milang@tal.org \
/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