From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54270) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeVbX-0002z2-6S for qemu-devel@nongnu.org; Fri, 11 Mar 2016 17:32:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aeVbW-0007bK-Do for qemu-devel@nongnu.org; Fri, 11 Mar 2016 17:32:19 -0500 Received: from mail-vk0-x22f.google.com ([2607:f8b0:400c:c05::22f]:35311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeVbW-0007ak-7A for qemu-devel@nongnu.org; Fri, 11 Mar 2016 17:32:18 -0500 Received: by mail-vk0-x22f.google.com with SMTP id e6so151203405vkh.2 for ; Fri, 11 Mar 2016 14:32:18 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Sat, 12 Mar 2016 05:31:58 +0700 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] Memory on stellaris board List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelio Remonda Cc: QEMU Developers On 11 March 2016 at 21:12, Aurelio Remonda wrote: > I don't quite understand what you mean with non-round-number, are you suggesting > we only accept for example: > 64K-128K-256K-512K-1024k(or 1M)-2048K(or 2M) > 4096K(or 4M)-8192K(or 8M)-16384K(or 16M) > If that's the case we will never have, for example, the exact default > dc0 value (0x00ff007f) What I am suggesting is that we should accept the memory sizes which correspond to what can be represented in dc0 (which presumably correspond to possible real hardware configurations) and not any memory sizes which can't be represented by a dc0 value. > because you need to divide the given size by 1024 reverting what the > prefix (K or M) have > done and then multiply this value by 1000. I don't know what you mean here, because ram_size is given to the board code as a value in bytes. The M and K prefix stuff is just user convenience when they specify values on the command line. thanks -- PMM