From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mex23-0000I6-6r for qemu-devel@nongnu.org; Sat, 22 Aug 2009 16:17:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mex1x-0000E4-Od for qemu-devel@nongnu.org; Sat, 22 Aug 2009 16:17:45 -0400 Received: from [199.232.76.173] (port=53340 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mex1x-0000Dz-Cz for qemu-devel@nongnu.org; Sat, 22 Aug 2009 16:17:41 -0400 Received: from mail-gx0-f211.google.com ([209.85.217.211]:50035) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mex1x-00039W-4X for qemu-devel@nongnu.org; Sat, 22 Aug 2009 16:17:41 -0400 Received: by gxk7 with SMTP id 7so1897010gxk.8 for ; Sat, 22 Aug 2009 13:17:40 -0700 (PDT) MIME-Version: 1.0 From: Artyom Tarasenko Date: Sat, 22 Aug 2009 22:17:20 +0200 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] sparc32 SIMM size List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Robert Reif Cc: Blue Swirl , qemu-devel > 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. =A0A smaller size will be mirrored > to fill the entire space and OBP checks for mirrioing to > determine the actual size. =A0QEMU doesn't do any mirroring > for small SIMMS which will confuse OBP. =A0I 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 .