From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
lersek@redhat.com, Magnus Damm <magnus.damm@gmail.com>,
mreitz@redhat.com, qemu-ppc@nongnu.org, alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 08/11] r2d: Flash memory creation is confused about size, mark FIXME
Date: Wed, 06 Mar 2019 16:00:51 +0100 [thread overview]
Message-ID: <8736o0vyho.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <71bfd7e6-abda-d26d-b3d3-e4c2ed9e98f8@redhat.com> ("Philippe Mathieu-Daudé"'s message of "Tue, 5 Mar 2019 18:48:51 +0100")
Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> On 2/26/19 8:34 PM, Markus Armbruster wrote:
>> pflash_cfi02_register() takes a size in bytes, a block size in bytes
>> and a number of blocks. r2d_init() passes FLASH_SIZE, 16 * KiB,
>> FLASH_SIZE >> 16. Does not compute: size doesn't match block size *
>> number of blocks. The latter happens to win. I tried to find
>> documentation on the physical hardware, no luck.
>>
>> For now, adjust the byte size passed to match the actual size created,
>> and add a FIXME comment.
>>
>> Cc: Magnus Damm <magnus.damm@gmail.com>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> hw/sh4/r2d.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/sh4/r2d.c b/hw/sh4/r2d.c
>> index dcdb3728cb..ed18d1f351 100644
>> --- a/hw/sh4/r2d.c
>> +++ b/hw/sh4/r2d.c
>> @@ -290,7 +290,14 @@ static void r2d_init(MachineState *machine)
>>
>> /* onboard flash memory */
>> dinfo = drive_get(IF_PFLASH, 0, 0);
>> - pflash_cfi02_register(0x0, NULL, "r2d.flash", FLASH_SIZE,
>> + /*
>> + * FIXME The code is confused about the size of the flash. It
>> + * used to pass FLASH_SIZE bytes, in FLASH_SIZE >> 16 blocks of
>> + * 16KiB each, which does not compute, but creates one of
>> + * FLASH_SIZE / 4 bytes anyway. The current code does so too, but
>> + * whether it's the right size is anybody's guess.
>> + */
>> + pflash_cfi02_register(0x0, NULL, "r2d.flash", FLASH_SIZE / 4,
>
> NAck, please see suggestion on v1:
> https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg01206.html
I'll use that to replace this patch in v3. Thanks!
[...]
next prev parent reply other threads:[~2019-03-06 15:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 19:33 [Qemu-devel] [PATCH v2 00/11] pflash: Fixes and cleanups Markus Armbruster
2019-02-26 19:33 ` [Qemu-devel] [PATCH v2 01/11] pflash: Rename pflash_t to PFlashCFI01, PFlashCFI02 Markus Armbruster
2019-03-05 12:22 ` Philippe Mathieu-Daudé
2019-02-26 19:33 ` [Qemu-devel] [PATCH v2 02/11] pflash_cfi01: Do not exit() on guest aborting "write to buffer" Markus Armbruster
2019-02-26 23:59 ` Philippe Mathieu-Daudé
2019-02-27 11:09 ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 03/11] pflash_cfi01: Log use of flawed " Markus Armbruster
2019-02-26 23:57 ` Philippe Mathieu-Daudé
2019-02-27 11:30 ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 04/11] pflash: Rename *CFI_PFLASH* to *PFLASH_CFI* Markus Armbruster
2019-02-27 0:00 ` Philippe Mathieu-Daudé
2019-02-27 11:09 ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 05/11] hw: Use PFLASH_CFI0{1, 2} and TYPE_PFLASH_CFI0{1, 2} Markus Armbruster
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 06/11] sam460ex: Don't size flash memory to match backing image Markus Armbruster
2019-02-26 22:30 ` BALATON Zoltan
2019-02-27 11:04 ` Alex Bennée
2019-03-05 19:12 ` Philippe Mathieu-Daudé
2019-03-05 22:49 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-03-06 6:51 ` Markus Armbruster
2019-03-06 7:47 ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 07/11] ppc405_boards: " Markus Armbruster
2019-02-27 10:35 ` Alex Bennée
2019-03-07 7:01 ` Markus Armbruster
2019-03-08 4:39 ` David Gibson
2019-03-08 9:46 ` Markus Armbruster
2019-03-05 19:23 ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 08/11] r2d: Flash memory creation is confused about size, mark FIXME Markus Armbruster
2019-03-05 17:48 ` Philippe Mathieu-Daudé
2019-03-06 15:00 ` Markus Armbruster [this message]
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 09/11] mips_malta: Clean up definition of flash memory size somewhat Markus Armbruster
2019-02-27 11:28 ` Alex Bennée
2019-03-05 16:33 ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 10/11] pflash: Clean up after commit 368a354f02b part 1 Markus Armbruster
2019-03-05 13:29 ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 11/11] pflash: Clean up after commit 368a354f02b part 2 Markus Armbruster
2019-02-27 1:11 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-02-27 6:57 ` Markus Armbruster
2019-03-05 13:55 ` [Qemu-devel] " Philippe Mathieu-Daudé
2019-03-05 16:42 ` Markus Armbruster
2019-03-05 17:54 ` Philippe Mathieu-Daudé
2019-02-26 19:56 ` [Qemu-devel] [PATCH v2 00/11] pflash: Fixes and cleanups Alex Bennée
2019-02-27 6:57 ` Markus Armbruster
2019-02-27 11:30 ` Alex Bennée
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=8736o0vyho.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=magnus.damm@gmail.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.