diff options
author | Marek Vasut <marex@denx.de> | 2023-01-05 16:08:23 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-01-12 22:06:16 +0300 |
commit | d0ba0ca45a49d6a062d0bc94b3380ea9b9616284 (patch) | |
tree | d9d1adf67f37b50b7a1ade3ef199bd467a039c63 /drivers/core | |
parent | ea3d28ec31d64cd059683947746ac71c8a90a1f9 (diff) | |
download | u-boot-d0ba0ca45a49d6a062d0bc94b3380ea9b9616284.tar.xz |
distro_bootcmd: Set distro_bootpart_uuid for block devices
The assignment of block device nodes in Linux is not deterministic by
default, i.e. a newly added eMMC controller or other block device can
change the assignment of /dev/mmcblkN (or other block device node like
e.g. /dev/sdXy) and prevent the system from picking the correct block
device for root filesystem in case the root filesystem is specified on
kernel command line using 'root=/dev/mmcblkNpM' (or 'root=/dev/sdXy'
etc.).
One way out is to derive PARTUUID in U-Boot, which is unique identifier
of a partition, and pass that as root=PARTUUID=<partuuid> to Linux via
kernel command line. Linux would then find the partition using PARTUUID,
no matter on which block device the partition resides and which node was
assigned to that block device.
Derive the PARTUUID before scanning for extlinux presence and assign it
into distro_bootpart_uuid environment variable, which can then be used
in extlinux.conf kernel command line specifier.
Note that it is not possible to do this in scan_dev_for_extlinux script
because this script is called from scan_dev_for_boot script, which is
called for both block devices as well as UBI volumes, and we can not
derive PARTUUID for UBI volumes.
Signed-off-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'drivers/core')
0 files changed, 0 insertions, 0 deletions