From: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Al Viro <viro@zeniv.linux.org.uk>, Jens Axboe <axboe@kernel.dk>,
s.hauer@pengutronix.de
Cc: linux-mmc@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Consistent block device references for root= cmdline
Date: Wed, 10 Jun 2020 15:15:03 +0200 [thread overview]
Message-ID: <fb0340aaf273be84e915214a3d8bae4ac85d7c0b.camel@ew.tq-group.com> (raw)
Hello all,
there have been numerous attempts to make the numbering of mmcblk
devices consistent, mostly by using aliases from the DTS ([1], [2],
[3]), but all have been (rightfully) rejected. Unless I have overlooked
a more recent development, no attempts for a different solution were
made.
As far as I can tell, the core of the issue seems to be the following:
The existing solutions like LABELs and UUIDs are viable alternatives in
many cases, but in particular on embedded systems, this is not quite
sufficient: In addition to the problem that more knowledge about the
system to boot is required in the bootloader, this approach fails
completely when the same firmware image exists on multiple devices, for
example on an eMMC and an SD card - not an entirely uncommon situation
during the development of embedded systems.
With udev, I can refer to a specific partition using a path like
/dev/disk/by-path/platform-2194000.usdhc-part2. In [4] it was proposed
to add a way to refer to a device path/phandle from the kernel command
line. Has there been any progress on this proposal?
Kind regards,
Matthias
[1] https://patchwork.kernel.org/patch/8685711/
[2] https://lore.kernel.org/patchwork/cover/674381/
[3] https://www.spinics.net/lists/linux-mmc/msg26586.html
[4] https://www.spinics.net/lists/linux-mmc/msg26708.html
next reply other threads:[~2020-06-10 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:15 Matthias Schiffer [this message]
2020-06-10 14:52 ` Consistent block device references for root= cmdline Ulf Hansson
2020-06-10 17:33 ` Roger Heflin
2020-06-11 11:23 ` (EXT) " Matthias Schiffer
2020-06-11 11:20 ` Matthias Schiffer
2020-07-07 14:14 ` Ulf Hansson
2020-07-29 8:43 ` (EXT) " Matthias Schiffer
2020-08-05 7:50 ` Ulf Hansson
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=fb0340aaf273be84e915214a3d8bae4ac85d7c0b.camel@ew.tq-group.com \
--to=matthias.schiffer@ew.tq-group.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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).