From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] pflash_cfi01/pflash_cfi02: convert to memory API
Date: Sun, 28 Aug 2011 20:14:04 +0200 [thread overview]
Message-ID: <20110828181404.GE11446@zapo> (raw)
In-Reply-To: <1314546216-26613-1-git-send-email-avi@redhat.com>
On Sun, Aug 28, 2011 at 06:43:36PM +0300, Avi Kivity wrote:
> cfi02 is annoying in that is ignores some address bits; we probably
> want explicit support in the memory API for that.
>
> In order to get the correct opaque into the MemoryRegion object, the
> allocation scheme is changed so that the flash emulation code allocates
> memory, instead of the caller. This clears a FIXME in the flash code.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
>
> This is a rework of the pflash conversion to the memory API. It has changed
> significantly - the change in allocation described above - so please review
> carefully.
>
> The mips_malta change also changes behavious - previously on of the two
> aliases was mapped as rom/device while the other was mapped as plain rom.
> Now both aliases are mapped as rom/device. I'm guessing that this is the
> right behaviour, and the old behaviour was just an implementation limitation,
> but if someone can check, that would be even better. That file has the most
> sensitive changes so please review it extra carefully.
Regarding the flash mapping, your description matches my understanding of it.
There is a difference between the 0x1fc and the 0x1e0 mappings though, in that
reading from 0x1fc00010 does not map to the flash but instead gets decoded
into a read from a revision register. To read from the flash at 0x10, you
need to go via the 0x1e0 mapping.
That was never modelled by QEMU, instead the malta board writes into the
backing ram of the flash area, see:
/* Board ID = 0x420 (Malta Board with CoreLV)
XXX: theoretically 0x1e000010 should map to flash and 0x1fc00010 should
map to the board ID. */
stl_p(memory_region_get_ram_ptr(bios) + 0x10, 0x00000420);
I assume this will continue to work even after your changes but it would be
good to test it. I can check it.
A problem, with my compiler I see this:
qemu/hw/mips_malta.c: In function ‘mips_malta_init’:
qemu/hw/mips_malta.c:860:37: error: ‘bios’ may be used uninitialized in this function [-Werror=uninitialized]
Cheers
next prev parent reply other threads:[~2011-08-28 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 15:43 [Qemu-devel] [PATCH] pflash_cfi01/pflash_cfi02: convert to memory API Avi Kivity
2011-08-28 18:14 ` Edgar E. Iglesias [this message]
2011-08-28 18:46 ` Edgar E. Iglesias
2011-08-29 5:35 ` Avi Kivity
2011-08-28 19:33 ` Edgar E. Iglesias
2011-08-29 5:36 ` Avi Kivity
2011-08-29 6:04 ` Edgar E. Iglesias
2011-08-29 6:13 ` Edgar E. Iglesias
2011-08-28 20:37 ` Edgar E. Iglesias
2011-08-29 5:38 ` Avi Kivity
2011-08-29 6:00 ` Edgar E. Iglesias
2011-08-29 6:15 ` Avi Kivity
2011-08-29 6:18 ` Edgar E. Iglesias
2011-08-29 7:21 ` Avi Kivity
2011-08-29 7:30 ` Edgar E. Iglesias
2011-08-29 8:15 ` Avi Kivity
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=20110828181404.GE11446@zapo \
--to=edgar.iglesias@gmail.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).