From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Guenter Roeck" <linux@roeck-us.net>,
"Cédric Le Goater" <clg@kaod.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Thomas Huth <thuth@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Joel Stanley <joel@jms.id.au>, qemu-block <qemu-block@nongnu.org>
Subject: Re: [PATCH 0/2] arm: Add collie and sx functional tests
Date: Mon, 28 Oct 2024 09:41:03 +0100 [thread overview]
Message-ID: <670fa7bf052d8f292f9bd25c330c8d7bdba02770.camel@pengutronix.de> (raw)
In-Reply-To: <4246f82b-597c-4a5d-9a55-18a584e7d8c7@roeck-us.net>
On Sun, 2024-10-27 at 20:32 -0700, Guenter Roeck wrote:
> On 10/27/24 15:26, Cédric Le Goater wrote:
> > On 10/27/24 23:11, Guenter Roeck wrote:
> > > On 10/27/24 14:13, Cédric Le Goater wrote:
> > > > On 10/26/24 17:32, Guenter Roeck wrote:
> > > > > On 10/26/24 03:02, Cédric Le Goater wrote:
> > > > > [ ... ]
> > > > >
> > > > > >
> > > > > Works for me, though, and it is much better than mandating the existence
> > > > > of boot partitions.
> > > >
> > > > Yes. However, if the emmc device was user creatable, we could use :
> > > >
> > > > -blockdev node-name=emmc0,driver=file,filename=mmc-ast2600-evb-noboot.raw \
> > > > -device emmc,bus=sdhci-bus.2,drive=emmc0
> > > >
> > > > and with boot partitions:
> > > >
> > > > -M boot-emmc=true \
> > > > -blockdev node-name=emmc0,driver=file,filename=mmc-ast2600-evb.raw \
> > > > -device emmc,bus=sdhci-bus.2,drive=emmc0,boot-partition-size=1048576,boot-config=8
> > > >
> > > > The above would be my preferred approach if acceptable. The "sd-bus"
> > > > bus identifier should be changed in other machines tough.
> > >
> > > No real preference here, though my understanding is that emmc devices
> > > are by definition built-in, and that is what emmc_class_init() says as well.
> > > Also, there does not seem to be an sdhci-bus, only sd-bus, and that does
> > > not support any index values. That may be just my lack of knowledge, though.
> >
> > No, you are right. On a real ast2600-evb, the eMMC device is indeed
> > soldered on the board. But, for testing purposes, it is sometime
> > interesting to add some flexibility in the machine definition and
> > in the modeling too. This avoids "hard-coding" default devices in
> > the machines and lets the user define its own variant models using
> > the QEMU command line.
>
> I would agree, but I had a number of my patches rejected because while
> they would be useful for testing they would not accurately reflect the
> hardware. So nowadays I gave up even trying to upstream such changes.
My patch to make eMMCs user creatable [1] was applied to target-
arm.next by Peter Maydell [2] last week.
Jan
[1] https://lore.kernel.org/qemu-devel/20241015135649.4189256-1-jlu@pengutronix.de/
[2] https://lore.kernel.org/qemu-devel/CAFEAcA9sjszCj=Fu-A-=qQV_jawnomJ-Nqnd=Vx2vLKmYZ1-nQ@mail.gmail.com/
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-10-28 8:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:32 [PATCH 0/2] arm: Add collie and sx functional tests Peter Maydell
2024-10-17 16:32 ` [PATCH 1/2] tests/functional: Add a functional test for the collie board Peter Maydell
2024-10-17 17:15 ` Thomas Huth
2024-10-22 4:11 ` Philippe Mathieu-Daudé
2024-10-22 7:09 ` Daniel P. Berrangé
2024-10-22 9:02 ` Peter Maydell
2024-10-22 21:45 ` Philippe Mathieu-Daudé
2024-10-17 16:32 ` [PATCH 2/2] tests/functional: Add a functional test for the sx1 board Peter Maydell
2024-10-17 17:18 ` Thomas Huth
2024-10-21 7:15 ` [PATCH 0/2] arm: Add collie and sx functional tests Thomas Huth
2024-10-21 8:01 ` Thomas Huth
2024-10-21 9:17 ` Peter Maydell
2024-10-21 9:40 ` Thomas Huth
2024-10-21 14:02 ` Guenter Roeck
2024-10-22 4:09 ` Philippe Mathieu-Daudé
2024-10-22 5:24 ` Guenter Roeck
2024-10-22 15:04 ` Guenter Roeck
2024-10-24 17:59 ` Philippe Mathieu-Daudé
2024-10-25 6:55 ` Cédric Le Goater
2024-10-25 9:57 ` Jan Lübbe
2024-10-25 13:59 ` Guenter Roeck
2024-10-25 15:25 ` Jan Lübbe
2024-10-25 17:05 ` Guenter Roeck
2024-10-26 4:47 ` Philippe Mathieu-Daudé
2024-10-26 5:54 ` Guenter Roeck
2024-10-26 10:02 ` Cédric Le Goater
2024-10-26 15:32 ` Guenter Roeck
2024-10-27 21:13 ` Cédric Le Goater
2024-10-27 22:11 ` Guenter Roeck
2024-10-27 22:26 ` Cédric Le Goater
2024-10-28 3:32 ` Guenter Roeck
2024-10-28 8:41 ` Jan Lübbe [this message]
2024-10-29 14:40 ` Guenter Roeck
2024-11-01 14:14 ` backing storage for eMMC boot partitions Jan Lübbe
2024-11-18 9:14 ` Cédric Le Goater
2024-11-18 12:15 ` Jan Lübbe
2024-11-18 12:36 ` Cédric Le Goater
2024-10-28 16:23 ` [PATCH] hw/sd/sdcard: Fix calculation of size when using " Jan Luebbe
2024-10-29 8:31 ` Cédric Le Goater
2024-11-02 15:06 ` Cédric Le Goater
2024-11-04 10:33 ` Philippe Mathieu-Daudé
2024-11-05 16:13 ` Michael Tokarev
2024-11-05 16:31 ` Cédric Le Goater
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=670fa7bf052d8f292f9bd25c330c8d7bdba02770.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).