From: Peter Maydell <peter.maydell@linaro.org>
To: Aurelio Remonda <aurelio.remonda@tallertechnologies.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Memory on stellaris board
Date: Thu, 10 Mar 2016 08:54:30 +0700 [thread overview]
Message-ID: <CAFEAcA8m0OBxu80jjCdT0Tt_qTE=xBYKSYBT7bTBFPitnBH=pA@mail.gmail.com> (raw)
In-Reply-To: <CANLssssp-cGn6nsr33nHSHuc4y2ccXA8MxTyskE=ScdUbnSVGQ@mail.gmail.com>
On 10 March 2016 at 07:23, Aurelio Remonda
<aurelio.remonda@tallertechnologies.com> wrote:
>
> El 9 mar. 2016 8:25 PM, "Peter Maydell" <peter.maydell@linaro.org> escribió:
>> 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áximum? I make sure that 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
next prev parent reply other threads:[~2016-03-10 1:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:00 [Qemu-devel] Memory on stellaris board Aurelio Remonda
2016-02-03 13:34 ` Peter Maydell
2016-02-03 13:45 ` Aurelio Remonda
2016-02-05 16:09 ` Aurelio Remonda
2016-02-05 16:23 ` Peter Maydell
2016-02-05 16:55 ` Aurelio Remonda
2016-02-05 17:00 ` Peter Maydell
2016-02-11 12:46 ` Aurelio Remonda
2016-02-11 13:01 ` Peter Maydell
2016-03-07 19:58 ` Aurelio Remonda
2016-03-07 23:37 ` Peter Maydell
2016-03-09 20:56 ` Aurelio Remonda
2016-03-09 23:24 ` Peter Maydell
2016-03-10 0:23 ` Aurelio Remonda
2016-03-10 1:54 ` Peter Maydell [this message]
2016-03-11 14:12 ` Aurelio Remonda
2016-03-11 22:31 ` Peter Maydell
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='CAFEAcA8m0OBxu80jjCdT0Tt_qTE=xBYKSYBT7bTBFPitnBH=pA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelio.remonda@tallertechnologies.com \
--cc=qemu-devel@nongnu.org \
/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).