From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55539) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adpoS-0004b1-Ay for qemu-devel@nongnu.org; Wed, 09 Mar 2016 20:54:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adpoR-0003zd-4C for qemu-devel@nongnu.org; Wed, 09 Mar 2016 20:54:52 -0500 Received: from mail-vk0-x22a.google.com ([2607:f8b0:400c:c05::22a]:33963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adpoQ-0003zV-Nk for qemu-devel@nongnu.org; Wed, 09 Mar 2016 20:54:51 -0500 Received: by mail-vk0-x22a.google.com with SMTP id e185so78850384vkb.1 for ; Wed, 09 Mar 2016 17:54:50 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Thu, 10 Mar 2016 08:54:30 +0700 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 10 March 2016 at 07:23, Aurelio Remonda wrote: > > El 9 mar. 2016 8:25 PM, "Peter Maydell" escrib= i=C3=B3: >> You should reject unworkable ram sizes rather than silently >> changing what the user asked for; this matches our preferred >> approach where the user asks for more RAM than the board >> can support. > > With unworkable you mean RAM values over dc0 m=C3=A1ximum? I make sure th= at it > does not exceed 0xffff before i replace the dc0 value so if it goes over = 16M > the program report the problem (via error_report()) and exit. Also if the user asks for a non-round-number ram size: don't round ram_size up or down, just fail if the user asked for something that's not representable in a dc0 value. thanks -- PMM