From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mez9e-0005Ik-P7 for qemu-devel@nongnu.org; Sat, 22 Aug 2009 18:33:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mez9Z-0005IF-8e for qemu-devel@nongnu.org; Sat, 22 Aug 2009 18:33:45 -0400 Received: from [199.232.76.173] (port=43307 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mez9Z-0005IC-2z for qemu-devel@nongnu.org; Sat, 22 Aug 2009 18:33:41 -0400 Received: from pop-cowbird.atl.sa.earthlink.net ([207.69.195.68]:53910) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mez9Y-0000tg-Jz for qemu-devel@nongnu.org; Sat, 22 Aug 2009 18:33:40 -0400 Message-ID: <4A907242.8020104@earthlink.net> Date: Sat, 22 Aug 2009 18:33:38 -0400 From: Robert Reif MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: sparc32 SIMM size List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: Blue Swirl , qemu-devel Artyom Tarasenko wrote: >> 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 . > > Look on page 71 Appendex AII Campus 2 (SS10) of the Sun4m System Architecture manual for an explanation: http://wikis.sun.com/display/FOSSdocs/Home