From: Francesco Lavra <francescolavra.fl@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH] Versatile Express: add modelling of NOR flash
Date: Mon, 17 Sep 2012 19:29:19 +0200 [thread overview]
Message-ID: <50575DEF.7070104@gmail.com> (raw)
In-Reply-To: <CAFEAcA-co8eT0VHCvnXSS465Pb48Ka-V0H6rQCJHRN5ttktsgQ@mail.gmail.com>
On 09/17/2012 03:21 PM, Peter Maydell wrote:
> On 5 September 2012 20:07, Francesco Lavra <francescolavra.fl@gmail.com> wrote:
>> Documentation at
>> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503c/CHDEFDJF.html
>> says that the entire first 512 MB can be mapped to either SMC (which is
>> the default) or AXI, so if AXI is selected neither of the 2 flash banks
>> is visible. Also, the same doc says that it's possible to map either
>> NOR0 (default) or NOR1 to the address 0x00000000. This implies that in
>> the A Series memory map VE_NORFLASH0 should be at 0x08000000 and
>> VE_NORFLASH0ALIAS at 0x00000000, not the other way around (by the way,
>> this is also how U-Boot defines the memory for the A5 CoreTile). Maybe
>> worth a patch?
>
> Agreed, NORFLASH0 should be at 0x08000000 in the new memory map. Unless
> anybody actually needs the aliasing of the flash at address zero, I
> suggest just deleting all references to VE_NORFLASH0ALIAS.
Ok, thanks, then I'm going to send a 2 patch series, which first will
fix NORFLASH0 and remove NORFLASH0ALIAS, and then will actually add the
flash modelling.
prev parent reply other threads:[~2012-09-17 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 17:08 [Qemu-devel] [PATCH] Versatile Express: add modelling of NOR flash Francesco Lavra
2012-09-05 5:16 ` Stefan Weil
2012-09-05 8:47 ` Peter Maydell
2012-09-05 19:07 ` Francesco Lavra
2012-09-15 7:45 ` Francesco Lavra
2012-09-17 13:21 ` Peter Maydell
2012-09-17 17:29 ` Francesco Lavra [this message]
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=50575DEF.7070104@gmail.com \
--to=francescolavra.fl@gmail.com \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).