Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Soren S. Jorvang" <soren@wheel.dk>
Cc: Florian Lohoff <flo@rfc822.org>, linux@cthulhu.engr.sgi.com
Subject: Re: O2 ARCS
Date: Thu, 18 May 2000 17:28:09 +0200	[thread overview]
Message-ID: <20000518172809.D1455@uni-koblenz.de> (raw)
In-Reply-To: <20000518151657.A5906@gnyf.wheel.dk>; from soren@wheel.dk on Thu, May 18, 2000 at 03:16:57PM +0200

On Thu, May 18, 2000 at 03:16:57PM +0200, Soren S. Jorvang wrote:

> 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 ?
> 
> While not quite identical to the SGI ARCS firmware, 
> http://www.microsoft.com/hwdev/download/respec/riscspec.zip
> is useful.

Staring at the winword file in this archive with strings this pretty much
looks like one of the dead tree copies I was using for my work, so it's
definately usable.  The ARC / ARCS differences are not too big, just look
into arch/mips/arc/ which handles them.  The differences between specs and
real world implementation is another thing - I haven't yet seen a single
implementation that conforms to the spec.  Which is why I believe the
ARC spec should best be locked up in Fort Knox ;-)

  Ralf

      reply	other threads:[~2000-05-18 15:39 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
2000-05-18 13:16     ` Soren S. Jorvang
2000-05-18 15:28       ` Ralf Baechle [this message]

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=20000518172809.D1455@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