qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Robert Reif <reif@earthlink.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc sun4m changes
Date: Thu, 13 Aug 2009 19:14:12 -0400	[thread overview]
Message-ID: <4A849E44.8090502@earthlink.net> (raw)
In-Reply-To: <f43fc5580908131154j75ad0690yf79a3018101408a@mail.gmail.com>

Blue Swirl wrote:
>> 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.
>>
>>     
>
> There has been no activity in a year, are all devices documented already?
>
>   
STP2013 and STP2014 (ss 10/20) are not documented.  I bought an
STP2014 manual off ebay.

The ss600mp documentation is pretty high level and not real useful.

  reply	other threads:[~2009-08-13 23:15 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
2009-08-13 18:54   ` Blue Swirl
2009-08-13 23:14     ` Robert Reif [this message]
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=4A849E44.8090502@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 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).