On 2022-06-02, Jochen Sprickerhof wrote:
> with the latest u-boot-exynos in unstable it tries to load
> exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
> contains exynos5422-odroidxu4.dtb. This was not the case with 2022.01+dfsg-2:
>
> U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +0000) for 
> ODROID-XU3/XU4/HC1/HC2
> [..]
> Retrieving file: 
> /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb
> ** File not found 
> /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb **
>
> U-Boot 2022.01+dfsg-2 (Jan 26 2022 - 19:58:27 +0000) for 
> ODROID-XU3/XU4/HC1/HC2
> [..]
> Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-odroidxu4.dtb

Thanks for bringing this up in IRC.

My guess is this was broken in 2022.04, and fixed in 2022.07-rc5 with
this commit:

commit e744bf3a4ba442a0e9ee1c509c70e1452e3a15d0
Author: Tom Rini <tr...@konsulko.com>
Date:   Wed Jun 8 14:30:14 2022 -0400

    odroid_xu3: Fix board environment variable

    When migrating CONFIG_CONS_INDEX to Kconfig, on this platform we changed
    what "board" evaluated to in the environment.  This in turn meant that
    we would no longer try and find the correct fdtfile via the normal
    distro boot logic.  Fix this by overriding board in the default
    environment, as done on other platforms where CONFIG_SYS_BOARD is not
    what we want to be in the board environment variable.

    Fixes: f76750d11133 ("Convert CONFIG_CONS_INDEX et al to Kconfig")
    Reported-by: Gabriel Hojda <gho...@yo2urs.ro>
    Tested-by: Gabriel Hojda <gho...@yo2urs.ro>
    Signed-off-by: Tom Rini <tr...@konsulko.com>

diff --git a/include/configs/odroid_xu3.h b/include/configs/odroid_xu3.h
index eb35d7b4ae..360815bc03 100644
--- a/include/configs/odroid_xu3.h
+++ b/include/configs/odroid_xu3.h
@@ -86,6 +86,7 @@
        "rootfstype=ext4\0" \
        "console=console=ttySAC2,115200n8\0" \
        "fdtfile=exynos5422-odroidxu3.dtb\0" \
+       "board=odroid\0" \
        "board_name=odroidxu3\0" \
        "mmcbootdev=0\0" \
        "mmcrootdev=0\0" \

Could you test 2022.10 from unstable and/or pull 2022.07 from
snapshots.debian.org and test it?


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature

Reply via email to