From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Cédric Le Goater" <clg@kaod.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Bin Meng" <bmeng.cn@gmail.com>,
qemu-block@nongnu.org, "Guenter Roeck" <linux@roeck-us.net>
Subject: Re: [PATCH] hw/sd/sdcard: Allow user creation of eMMCs
Date: Fri, 08 Nov 2024 10:29:43 +0100 [thread overview]
Message-ID: <eaf053e4fa01827a188bfa5abe3af92e1f90fabd.camel@pengutronix.de> (raw)
In-Reply-To: <CAFEAcA_a4bYU=KQbKQmWtqvPF3fmtttbhgi0BB0hS1wcCV_U4w@mail.gmail.com>
On Tue, 2024-10-29 at 15:06 +0000, Peter Maydell wrote:
> On Fri, 18 Oct 2024 at 16:42, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On Tue, 15 Oct 2024 at 14:57, Jan Luebbe <jlu@pengutronix.de> wrote:
> > > For testing eMMC-specific functionality (such as handling boot
> > > partitions), it would be very useful to attach them to generic VMs such
> > > as x86_64 via the sdhci-pci device:
> > > ...
> > > -drive if=none,id=emmc-drive,file=emmc.img,format=raw \
> > > -device sdhci-pci \
> > > -device emmc,id=emmc0,drive=emmc-drive,boot-partition-size=1048576 \
> > > ...
> > >
> > > While most eMMCs are soldered to boards, they can also be connected to
> > > SD controllers with just a passive adapter, such as:
> > > https://docs.radxa.com/en/accessories/emmc-to-usd
> > > https://github.com/voltlog/emmc-wfbga153-microsd
> > >
> > > The only change necessary to make the options above work is to avoid
> > > disabling user_creatable, so do that. The SDHCI-PCI driver in the Linux
> > > kernel already supports this just fine.
> > >
> > > Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
> >
> > Applied to target-arm.next, thanks (unless anybody would
> > prefer it to go via some other route).
>
> I'm dropping this from target-arm.next since it seems like
> we have a problem with the handling of boot partitions
> and how the user should provide an image for an emmc card
> that has boot partitions). Since that's an emmc specific
> thing, sorting that out with a minimum of breaking
> compatibility with previously working setups is going to
> be easier if we stay temporarily in the state of "emmc
> only happens for the specific board that creates them
> and the user can't arbitrarily create them on the
> command line".
>
> I expect this to just be a temporary delay while we sort
> out in the other thread how emmc boot partitions should work.
With Cédric's e8f3acdbb8 ("aspeed: Don't set always boot properties of the emmc
device") and my c078298301 ("hw/sd/sdcard: Fix calculation of size when using
eMMC boot partitions") in master, compatibility for existing setups should be
taken care of.
As mentioned in Cédric's patch, allowing user creatable eMMC devices is still
desirable. With my patch, that would work for machines where the SD controller
is user-created as well (e.g. x86_64 with sdhci-pci).
For machines where the SD controller and SD/eMMC are pre-created, additional
changes seem to be needed. Would you consider taking this patch to solve the
simple case first?
Thanks,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-11-08 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 13:56 [PATCH] hw/sd/sdcard: Allow user creation of eMMCs Jan Luebbe
2024-10-15 15:00 ` Philippe Mathieu-Daudé
2024-10-15 15:17 ` Cédric Le Goater
2024-10-15 15:20 ` Daniel P. Berrangé
2024-10-15 15:42 ` Cédric Le Goater
2024-10-18 15:42 ` Peter Maydell
2024-10-19 15:31 ` Philippe Mathieu-Daudé
2024-10-29 15:06 ` Peter Maydell
2024-11-08 9:29 ` Jan Lübbe [this message]
2024-11-08 10:47 ` 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=eaf053e4fa01827a188bfa5abe3af92e1f90fabd.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=bmeng.cn@gmail.com \
--cc=clg@kaod.org \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-block@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).