From: Peter Maydell <peter.maydell@linaro.org>
To: Peter Delevoryas <peter@pjd.dev>
Cc: clg@kaod.org, andrew@aj.id.au, joel@jms.id.au,
qemu-arm@nongnu.org, qemu-devel@nongnu.org, patrick@stwcx.xyz,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 0/1] hw/arm/aspeed: Automatically zero-extend flash images
Date: Tue, 15 Nov 2022 10:48:40 +0000 [thread overview]
Message-ID: <CAFEAcA9itEDTrznX1KRVEza__Dch95aBpPzbdTJ0-tuxwiHtoQ@mail.gmail.com> (raw)
In-Reply-To: <20221114190823.1888691-1-peter@pjd.dev>
On Mon, 14 Nov 2022 at 19:08, Peter Delevoryas <peter@pjd.dev> 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.
We just had a thread about this kind of thing for one of the
riscv boards (although there the attempted approach was to
change the size of the flash device to match the provided
file, rather than changing the file to match the flash device):
https://lore.kernel.org/qemu-devel/20221107130217.2243815-1-sunilvl@ventanamicro.com/
The short summary is (a) yes, it's controversial and
(b) if we do something for this we need to have a standard
approach that we do on all boards, not "some boards do
some weird magic in different ways from everything else"...
thanks
-- PMM
next prev parent reply other threads:[~2022-11-15 10:49 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 ` Peter Maydell [this message]
2022-11-15 18:30 ` [PATCH 0/1] " 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
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=CAFEAcA9itEDTrznX1KRVEza__Dch95aBpPzbdTJ0-tuxwiHtoQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=andrew@aj.id.au \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=patrick@stwcx.xyz \
--cc=peter@pjd.dev \
--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).