From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Robert Reif <reif@earthlink.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] sparc32 SIMM size
Date: Sat, 22 Aug 2009 22:17:20 +0200 [thread overview]
Message-ID: <fb8d4f70908221317v3b3bb800s7e82595d3e6fe9ad@mail.gmail.com> (raw)
> You have to be careful when specifing a memory size on
> the ss10/20 because a SIMM slot uses 64M reguardless of
> the actual size of the SIMM. A smaller size will be mirrored
> to fill the entire space and OBP checks for mirrioing to
> determine the actual size. QEMU doesn't do any mirroring
> for small SIMMS which will confuse OBP. I don't think
> that is the issue are seeing but just something to keep in mind.
It's not an issue for SS-10/20, but may be an issue for SS-5 and
below. SS-5 and earlier support maximal SIMM size of 32M. It doesn't
seem to be reflected in hw/sun4m.c .
next reply other threads:[~2009-08-22 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 20:17 Artyom Tarasenko [this message]
2009-08-22 22:33 ` [Qemu-devel] Re: sparc32 SIMM size Robert Reif
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=fb8d4f70908221317v3b3bb800s7e82595d3e6fe9ad@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=reif@earthlink.net \
/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).