Star1
0
代码
代码
Issues
Pull Requests
项目讨论
Wiki
分析
Star1
0
IIgorudoo: bump u-boot v2017.11 -> v2026.07-rc4 (pilot)
d1c31d53创建于 7月1日历史提交
文件最后提交记录最后更新时间
README.md
udoo: bump u-boot v2017.11 -> v2026.07-rc4 (pilot) The imx6 family pins udoo to u-boot v2017.11, which no longer builds on trixie (Python 3.13 dropped distutils -> pylibfdt setup.py fails; also the SWIG 4.3 pylibfdt break). Bump udoo to the modern mainline u-boot, which builds cleanly. imx6.conf sets udoo's BOOTBRANCH in a `case $BOARD` sourced after the board file, so the override lives in a post_family_config hook: - BOOTBRANCH tag:v2026.07-rc4 - BOOTPATCHDIR v2026.07-imx6 (fresh, empty - the legacy/u-boot-imx6 v2017.11 patchset does not forward-apply) - UBOOT_TARGET_MAP sources u-boot-dtb.img (modern udoo_defconfig is DM/OF_CONTROL) into the existing u-boot.img.sdhc slot Boot-flow fix: upstream udoo_defconfig has SPL load u-boot-dtb.img from an EXT4 filesystem, but Armbian's write_uboot_platform dd's u-boot to a raw 69 KiB offset. A post_config_uboot_target hook switches SPL to raw-sector load (disable SPL_FS_EXT4/FAT, enable SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR). The MX6 default raw sector is 0x8a (=sector 138 = 69 KiB), matching the dd seek exactly, so no offset tuning is needed. Uses the upstream udoo_defconfig + imx6q-udoo DT as-is; all toggled symbols verified present in v2026.07-rc4. NOT yet hardware-tested - the SPL raw-load alignment is the thing to confirm on a board. Signed-off-by: Igor Pecovnik <igor@armbian.com>
2 个月前
README

v2026.07-imx6 — modern u-boot patch dir for bumped i.MX6 boards

Intentionally (almost) empty. Used by boards moved off the legacy imx6 u-boot (legacy/u-boot-imx6, pinned to v2017.11) onto a modern u-boot (v2026.07-rc4) that builds on Debian trixie — the old pylibfdt setup.py fails on Python 3.13 (distutils removed) and against SWIG 4.3.

Currently used by udoo only (pilot bump; see config/boards/udoo.csc). The upstream udoo_defconfig + imx6q-udoo DT are used as-is; Armbian-specific tweaks (SPL raw-sector load to match the raw-dd write_uboot_platform layout) are applied via post_config_uboot_target in the board file, not as patches.

Add real patches here only if a board needs a source change that can't be done through defconfig.