9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: northern snowfall <dbailey27@ameritech.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Rub your feet on the carpet!
Date: Wed,  1 Oct 2003 23:33:10 -0500	[thread overview]
Message-ID: <3F7BAA86.6080007@ameritech.net> (raw)
In-Reply-To: <3F7B8C11.6090503@Princeton.EDU>

> Wouldn't a SPARC architecture manual suffice? (Mine's at work so I
> can't check to see if it contains anything specific about the device
> in question...)

Yes and no. The SPARC architecture defines the generic rules
for designing a SPARCv8 implementation, but does leave much up
to the designer. For example:

    + MMU implementation can be either the SPARC reference MMU
      or an implementation of the designer's choice. The capability
      of the MMU has a huge impact on the design of supervisor code,
      obviously.

    + Ancillary registers for implementation specific functionality
      are left up to the designer as to use

    + much Coprocessor/FPU functionality is implementation dependent.
      The MB86903 has an onboard FPU, but I have no details on its
      specific capability.

There are other important facets that are implementation specific
and not bound to choices defined in the manual. Of course, the
general functionality of this SPARC CPU is v8 compatible. However,
I'd love to know what else the item is capable of. For example, the
IPX that were shipped with the Weitek CPU have an AT&T MMU on the
board. My IPX seem to have an LSI chip where the AT&T MMU should
be. I'm assuming this means the LSI WK34430P is the MMU, but I don't
know for sure. Google isn't pulling any info.

Also, this CPU is SPARCv7, which makes me even more interested in
specifics.

Don

http://www.7f.no-ip.com/~north_

Debug period.





  parent reply	other threads:[~2003-10-02  4:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 21:25 northern snowfall
2003-10-02  2:23 ` Martin Harriss
2003-10-02  4:07   ` ron minnich
2003-10-02  7:04     ` boyd, rounin
2003-10-02  8:15       ` northern snowfall
2003-10-02  8:58         ` Charles Forsyth
2003-10-02  8:16       ` northern snowfall
2003-10-02 13:58       ` ron minnich
2003-10-02  4:33   ` northern snowfall [this message]
2003-10-02  3:54     ` Bruce Ellis

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=3F7BAA86.6080007@ameritech.net \
    --to=dbailey27@ameritech.net \
    --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).