diff options
author | Jan-Niklas Burfeind <git@aiyionpri.me> | 2022-12-20 16:43:23 +0100 |
---|---|---|
committer | Stijn Tintel <stijn@linux-ipv6.be> | 2022-12-22 13:33:47 +0200 |
commit | bf06a7c865531cf20735cbdfac46d4947fcc18a6 (patch) | |
tree | 7842d0842cd3c4ec7e77b275cdd19e9c353cea04 /scripts/gen_image_generic.sh | |
parent | 5b82eeb320d9f8e543232bb5dd004e644b35983e (diff) | |
download | upstream-bf06a7c865531cf20735cbdfac46d4947fcc18a6.tar.gz upstream-bf06a7c865531cf20735cbdfac46d4947fcc18a6.tar.bz2 upstream-bf06a7c865531cf20735cbdfac46d4947fcc18a6.zip |
uboot-sunxi: use UUID of bootdev and bootpart
Several sunxi devices come with multiple mmc devices. On such devices,
the mmc device order is unpredictable, so using /dev/mmcblk0p2 as root
device doesn't always work, which results in unbootable devices.
For the Banana Pi BPI-R3 in the mediatek target, this has been solved by
defining aliases for the mmc devices in the DTS. Ideally we would do the
same here, but for sunxi-a64 we already use UUID probing, so let's start
with that (5f2ff607e286 ("uboot-sunxi: a64: allow booting directly from
eMMC")).
Since we're building and including u-boot in each supported device
image, and this method has been proven to work fine for a64, let's just
change the default u-boot env file to do the same.
Fixes: #10080
Fixes: e6d9f6fdff ("sunxi: add support for FriendlyARM NanoPi R1")
Co-authored-by: Karl Palsson <karlp@etactica.com>
Signed-off-by: Jan-Niklas Burfeind <git@aiyionpri.me>
[use UUID in default u-boot env, rewrite commit message]
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Diffstat (limited to 'scripts/gen_image_generic.sh')
0 files changed, 0 insertions, 0 deletions