All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] sparc sun4m changes
Date: Sun, 09 Aug 2009 22:28:04 -0400	[thread overview]
Message-ID: <4A7F85B4.5050406@earthlink.net> (raw)
In-Reply-To: <4A7F7E91.5000903@earthlink.net>

Robert Reif wrote:
> I just took a look at the sun4m interrupt controller and noticed
> the recent changes.  There are at least 3 different interrupt
> controllers used by sun4m: ss600mp with VME and MBUS
> specific support, ss 10/20 with MBUS support and ss 4/5/lx
> with slavio support.  This doesn't even address the java stations.
>
> intbit_to_level in slavio_intctrl.c needs to be different for each
> controller chip used.  There also needs to be a controller specific
> interrupt mask used.
>
> The NCR slavio chip is only used for single processor systems
> (ss 4/5/lx).  It is a subset of the ss 10/20 which is a subset of the
> ss600mp.  We really should address these differences.
>
I forgot to mention the ss 10/20 uses an STP 2014 SBus to EBus
Interface Controller.  I have a paper copy of the User's Guide.  I
can have it scanned to a pdf if necessary.

The ss600mp uses ASICs with no documentation other than
the sun4m System Architecture manual and SPARCsystem 600MP
VMEbus Implementation Guide on:
http://wikis.sun.com/display/FOSSdocs/Home.

  reply	other threads:[~2009-08-10  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10  1:57 [Qemu-devel] sparc sun4m changes Robert Reif
2009-08-10  2:28 ` Robert Reif [this message]
2009-08-13 18:54   ` Blue Swirl
2009-08-13 23:14     ` Robert Reif
2009-08-13 18:18 ` [Qemu-devel] " Blue Swirl

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=4A7F85B4.5050406@earthlink.net \
    --to=reif@earthlink.net \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.