From: ralf@uni-koblenz.de
To: kyriazis@sgi.com, "Fernando D. Mato Mira" <matomira@acm.org>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: XZ
Date: Tue, 20 Oct 1998 03:41:38 +0200 [thread overview]
Message-ID: <19981020034138.E676@uni-koblenz.de> (raw)
In-Reply-To: <199810191953.MAA90956@jibe.engr.sgi.com>; from George Kyriazis on Mon, Oct 19, 1998 at 12:53:40PM -0700
On Mon, Oct 19, 1998 at 12:53:40PM -0700, George Kyriazis wrote:
> * The monitor PROM downloads a mini-microcode that could be used. I am
> not sure what the entry points look like to the PROM. I think this
> is the safest bet.
> * Documentation will be hard to find. Documentation for programming the
> microcoded engines, even harder. You could, of course, use the existing
> microcode.
For now that looks like the best strategy. Anyway, as step one all we
want is text output. This can be achived by using the ARC firmware.
That may be slow, but it's working and it gives us an instant driver for
any number of console devices people might have come up with in the past.
The Sparc guys, btw already have a prom console driver.
Ralf
next prev parent reply other threads:[~1998-10-20 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-15 20:50 Partial Success Report Jeff Coffin
1998-10-15 22:17 ` Ulf Carlsson
1998-10-15 23:46 ` Jeff Coffin
1998-10-16 19:46 ` Ulf Carlsson
1998-10-17 1:15 ` XZ Jeremy John Welling
1998-10-17 9:17 ` XZ Thomas Bogendoerfer
1998-10-17 23:56 ` XZ ralf
1998-10-18 17:32 ` XZ George Kyriazis
1998-10-18 23:10 ` XZ ralf
1998-10-19 0:15 ` XZ William J. Earl
1998-10-19 6:44 ` XZ Fernando D. Mato Mira
1998-10-19 19:53 ` XZ George Kyriazis
1998-10-19 19:53 ` XZ George Kyriazis
1998-10-20 1:41 ` ralf [this message]
1998-10-17 2:01 ` Partial Success Report ralf
1998-10-18 0:09 ` Ulf Carlsson
1998-10-19 0:15 ` William J. Earl
1998-10-19 0:13 ` William J. Earl
1998-10-17 9:16 ` Thomas Bogendoerfer
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=19981020034138.E676@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=kyriazis@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=matomira@acm.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