From: Bob Breuer <breuerr@mc.net>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/2] Pad iommu with an empty slot (necessary for SunOS 4.1.4)
Date: Thu, 27 May 2010 11:34:21 -0500 [thread overview]
Message-ID: <4BFE9F0D.5090205@mc.net> (raw)
In-Reply-To: <AANLkTinjYiD1iUO1Q-Gw-yPPoyOleQX0qC9_r833nezL@mail.gmail.com>
Artyom Tarasenko wrote:
> Was going to put some more empty slots into SS-10/20 (VSIMMs, SX)
> after we are done with SS-5 (due to technical limitations I can switch
> access from one real SS model to another one once a few days only).
>
I have a partial implementation of the SS-20 VSIMM (cg14) that I've been
working on. With the Sun firmware, I have working text console, color
boot logo, and programmable video resolutions up to 1600x1280.
Bob
next prev parent reply other threads:[~2010-05-27 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 14:10 [Qemu-devel] [PATCH 1/2] Pad iommu with an empty slot (necessary for SunOS 4.1.4) Artyom Tarasenko
2010-05-08 14:10 ` [Qemu-devel] [PATCH 2/2] reformatted SS-5 and LX definitions Artyom Tarasenko
2010-05-09 7:44 ` [Qemu-devel] " Blue Swirl
2010-05-09 7:30 ` [Qemu-devel] Re: [PATCH 1/2] Pad iommu with an empty slot (necessary for SunOS 4.1.4) Blue Swirl
2010-05-09 8:29 ` Artyom Tarasenko
2010-05-09 8:48 ` Blue Swirl
2010-05-09 22:32 ` Artyom Tarasenko
2010-05-10 18:27 ` Blue Swirl
2010-05-10 20:51 ` Artyom Tarasenko
2010-05-10 21:05 ` Blue Swirl
2010-05-21 17:23 ` Artyom Tarasenko
2010-05-21 21:12 ` Blue Swirl
2010-05-25 17:00 ` Artyom Tarasenko
2010-05-25 19:56 ` Blue Swirl
2010-05-26 19:04 ` Artyom Tarasenko
2010-05-27 16:34 ` Bob Breuer [this message]
2010-05-28 21:53 ` Artyom Tarasenko
2010-05-29 8:23 ` 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=4BFE9F0D.5090205@mc.net \
--to=breuerr@mc.net \
--cc=atar4qemu@googlemail.com \
--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).