> I have installed fedora 31 on my Odroid XU4. However I have noticed a > problem with the uboot image in uboot-images-armv7 (2019.10). I have > used the uboot image /usr/share/uboot/odroid-xu3/u-boot.bin and I have > found it has the fdtfile environment variable set to > "exynos5422-odroid.dtb". In checking the boot partition of the fedora > system the dtb directory does not contain exynos5422-odroid.dtb. > > > My work around is to create a link from exynos5422-odroid.dtb to > exynos5422-odroidxu4.dtb in the dtb directory. Another is to edit the > fdtfile environment at the uboot prompt when booting the XU4. > > > Neither of the above are really satisfactory as the link needs creating > again when there is a kernel update. editing the variable at the boot > prompt is even worse as it needs to be done for every boot. > > > Is there a better way I can fix this or does the uboot-images-armv7 > package need fixing? The Odroid devices are community supported and we essentially just build the upstream U-Boot. I suspect you actually need to use the odroid-xu3 target rather than odroid one. I would think that there would be some detection logic to select the right device tree as there's a number of devices supported with a single U-Boot target. Overall the odroid devices are community/best effort support as the upstream isn't particularly great, don't engage and doing things pretty hostile to open source. We can't support them OOTB because there's non redistributable binaries needed and I'm not aware of any of the core arm team that actually have any of their devices. Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
