From: Aurelio Remonda <aurelio.remonda@tallertechnologies.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Memory on stellaris board
Date: Wed, 3 Feb 2016 10:45:10 -0300 [thread overview]
Message-ID: <CANLsssumQX9muKaKdArYDV=ex_=tTGexS=jJd_OA_uh+KQvDdQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8dZOGsEZ3smegTeiAZgGBMpkXZDymZwfScGJvBifFEFg@mail.gmail.com>
On Wed, Feb 3, 2016 at 10:34 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 3 February 2016 at 13:00, Aurelio Remonda
> <aurelio.remonda@tallertechnologies.com> wrote:
>> Hello, i was trying to understand how does the sram and flash size
>> works on lm3s6965evb, i found a hardcoded 0x00ff007f as dc0 value and
>> how flash_size and sram_size are calculated based on that hexadecimal.
>> I mean this:
>>
>> flash_size = (((board->dc0 & 0xffff) + 1) << 1) * 1024;
>> sram_size = ((board->dc0 >> 18) + 1) * 1024;
>> On stellaris.c
>>
>> When i use the -m [size] flag while running qemu how does the flag
>> affect does flash_size and sram_size values? Or it doesn't? Where can
>> i see that the memory has indeed change?
>
> This board model ignores -m. We just implement a model of this particular
> bit of hardware, which has a fixed amount of RAM in it.
Thanks for the quick answer, do you think it is worth to make the m
flag work for this model?
Can you give me a hint on where to look?(another board that use it) so
i can add this feature
for this model.
Thanks!
--
Aurelio Remonda
Software Engineer
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54-351-4217888 / 4218211
next prev parent reply other threads:[~2016-02-03 13:45 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 [this message]
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
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='CANLsssumQX9muKaKdArYDV=ex_=tTGexS=jJd_OA_uh+KQvDdQ@mail.gmail.com' \
--to=aurelio.remonda@tallertechnologies.com \
--cc=peter.maydell@linaro.org \
--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).