From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: "Soren S. Jorvang" <soren@wheel.dk>, linux@cthulhu.engr.sgi.com
Subject: Re: O2 ARCS
Date: Thu, 18 May 2000 13:47:35 +0200 [thread overview]
Message-ID: <20000518134735.A1078@uni-koblenz.de> (raw)
In-Reply-To: <20000518011656.A721@paradigm.rfc822.org>; from flo@rfc822.org on Thu, May 18, 2000 at 01:16:56AM +0200
On Thu, May 18, 2000 at 01:16:56AM +0200, Florian Lohoff wrote:
> On Wed, May 17, 2000 at 09:53:11PM +0200, Ralf Baechle wrote:
> > The ARCS firmware isn't the big deal but the R10000 support for this
> > system or any other non-cachecoherent system. Harald Koerfgen has
> > started poking at an O2 port and he's got first success.
>
> BTW: Is there any Documentation for the ARC Firmware of the SGIs ?
I've got various dead tree document which document ARC.
First there is the ARC standard, a document which is Microsoft and ACE
copyrighted. This also defines various hardware properties like plugs,
screen resolution, audio etc. These were already fairly lowend by '94
when I first saw the document. Consequentially a new standard was
named ``Microsoft Portable Bootloader Standard'' was created which
essentially is just most of the software parts from the full ARC
standard. Both documents are completly NT centric. In the meantime I
somewhere saw a newer version of the ARC standard which afair is
copyrighted by some publishing company (Addison Wesley?). Not sure if
it was actually published as a book. Finally there is SGI's variant
ARCS which is big endian and has various other minor changes from the
Portable Bootloader Standard. I don't know of any documentation.
Not all SGI machines do even use ARCS. The older ones have a MIPS-style
firmware, more current ones like the Origin have a ``enhanced subset''
of ARCS. Look into include/asm-mips64/sn/kl{config,dir}.h to find
how those datastructures look. On the Origin for example quering the
ARCS configuration tree doesn't work at all. For this new style
configuration information there is not much more documentatin available
than these IRIX header files.
Ralf
next prev parent reply other threads:[~2000-05-18 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-17 3:15 O2 ARCS Soren S. Jorvang
2000-05-17 19:53 ` Ralf Baechle
2000-05-17 23:16 ` Florian Lohoff
2000-05-18 11:47 ` Ralf Baechle [this message]
2000-05-18 13:16 ` Soren S. Jorvang
2000-05-18 15:28 ` Ralf Baechle
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=20000518134735.A1078@uni-koblenz.de \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux@cthulhu.engr.sgi.com \
--cc=soren@wheel.dk \
/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