From: "Cédric Le Goater" <clg@kaod.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Delevoryas" <peter@pjd.dev>
Cc: <peter.maydell@linaro.org>, <andrew@aj.id.au>, <joel@jms.id.au>,
<qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
<patrick@stwcx.xyz>,
Francisco Iglesias <frasse.iglesias@gmail.com>,
Alistair Francis <alistair@alistair23.me>
Subject: Re: [PATCH 0/1] hw/arm/aspeed: Automatically zero-extend flash images
Date: Tue, 15 Nov 2022 15:16:53 +0100 [thread overview]
Message-ID: <199aba7e-2ded-0309-45fd-d51c87c8eb5c@kaod.org> (raw)
In-Reply-To: <58687845-716a-76d0-a294-ffa26114ada0@linaro.org>
On 11/15/22 15:06, Philippe Mathieu-Daudé wrote:
> On 15/11/22 14:06, Cédric Le Goater wrote:
>> Hello Peter,
>>
>> On 11/14/22 20:08, Peter Delevoryas wrote:
>>> I've been using this patch for a long time so that I don't have to use
>>> dd to zero-extend stuff all the time. It's just doing what people are
>>> doing already, right? I hope it's not controversial.
>>
>> I simply run :
>>
>> truncate --size <size>
>>
>> on the FW file when needed and it is rare because most FW image builders
>> know the flash size of the target.
>>
>> However, the current error message is confusing and the following could
>> be an improvement :
>>
>> @@ -1606,6 +1606,13 @@ static void m25p80_realize(SSIPeripheral
>> if (s->blk) {
>> uint64_t perm = BLK_PERM_CONSISTENT_READ |
>> (blk_supports_write_perm(s->blk) ? BLK_PERM_WRITE : 0);
>> +
>> + if (blk_getlength(s->blk) != s->size) {
>
> '!=' -> '<' ?
Hey. yes :)
I will send a patch. I am not sure this is 7.2 material though.
Thanks,
C.
next prev parent reply other threads:[~2022-11-15 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 19:08 [PATCH 0/1] hw/arm/aspeed: Automatically zero-extend flash images Peter Delevoryas
2022-11-14 19:08 ` [PATCH 1/1] " Peter Delevoryas
2022-11-15 10:48 ` [PATCH 0/1] " Peter Maydell
2022-11-15 18:30 ` Peter Delevoryas
2022-11-15 13:06 ` Cédric Le Goater
2022-11-15 14:06 ` Philippe Mathieu-Daudé
2022-11-15 14:16 ` Cédric Le Goater [this message]
2022-11-15 20:06 ` Peter Delevoryas
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=199aba7e-2ded-0309-45fd-d51c87c8eb5c@kaod.org \
--to=clg@kaod.org \
--cc=alistair@alistair23.me \
--cc=andrew@aj.id.au \
--cc=frasse.iglesias@gmail.com \
--cc=joel@jms.id.au \
--cc=patrick@stwcx.xyz \
--cc=peter.maydell@linaro.org \
--cc=peter@pjd.dev \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.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).