From: Sascha Hauer <s.hauer@pengutronix.de>
To: Giorgio Dal Molin <giorgio.nicole@arcor.de>
Cc: barebox@lists.infradead.org
Subject: Re: eMMC partitions kernel comand line
Date: Thu, 18 Jun 2020 15:18:35 +0200 [thread overview]
Message-ID: <20200618131835.GK11869@pengutronix.de> (raw)
In-Reply-To: <1925287845.342649.1592468544667@mail.vodafone.de>
Hi Giorgio,
On Thu, Jun 18, 2020 at 10:21:12AM +0200, Giorgio Dal Molin wrote:
> Hallo,
>
> I'm working on an arm IMX7 module with an eMMC flash on it.
>
> I don't need/want to have a partition table on the eMMC, some hardcoded
> partitions are just OK. I've already defined them in the barebox device tree
> and it works, for barebox:
>
> ...
> partition@0 {
> label = "bl_env";
> reg = <BLENV_OFS BLENV_SIZE>;
> };
> partition@1 {
> label = "boot";
> reg = <BOOT_OFS BOOT_SIZE>;
> };
> ...
>
> Unfortunately the same trick is not supported by the linux kernel.
> What works for the kernel is the special command line option:
>
> blkdevparts=mmcblk1:1M(bl_env),50M(boot),...
>
> My question is: is it possible to let barebox automatically generate
> this command line according to what it has in its device tree or do I
> have to do it manually.
No, this is currently not possible, at least not without adding this
feature to barebox. Note that barebox doesn't know which MMC device
corresponds to "mmcblk1" as it depends on the initialization order in
Linux which MMC ends up as "mmcblk1".
It might be worth trying to add device tree partitioning support for
MMCs to Linux. The command line option was accepted also, so why not
device tree?
Regards,
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-06-18 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 8:21 Giorgio Dal Molin
2020-06-18 13:18 ` Sascha Hauer [this message]
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=20200618131835.GK11869@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=giorgio.nicole@arcor.de \
/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