| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
recomputer-rk35xx: u-boot: canonicalize patch headers via rewrite-uboot-patches | 14 天前 | |
add community support for MediaTek Filogic device (BananaPi R4 Router) | 1 年前 | |
genio: u-boot: mt8195 (nio-12l): update addr's map patch for large kernels/initrds - for extlinux/pxelinux scenarios (matching recently-updated bootscript boot.scr for genio) | 2 个月前 | |
board: beaglebadge: harden SSD16xx refresh handling Propagate Linux panel-ready and SPI failures, reject unmapped framebuffers, and periodically run a full anti-ghosting refresh. Keep U-Boot video synchronization unconditional by default, opt SSD16xx into rate limiting, and cover forced synchronization in the sandbox test. Rebase the splash patch over the new video operations. Developed with assistance from OpenAI Codex. Signed-off-by: Andrei Aldea <andrei1998@gmail.com> | 25 天前 | |
replace patch From: headers across the framework with something meaningful | 15 天前 | |
patches: u-boot: meson-s4t7: Update u-boot patch set * Defconfig additions CONFIG_CMD_SETEXPR CONFIG_CMD_UUID CONFIG_CMD_FS_UUID Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 7 天前 | |
board: add Nuvoton MA35D1 NuMaker IoT board support Add support for Nuvoton MA35D1 SoC family: - ARM Cortex-A35 dual-core @ 800MHz + Cortex-M4 heterogeneous - NuMaker IoT MA35D16F90 board (512MB DDR) - Vendor kernel 5.10.140 from Nuvoton GitHub - TF-A (BL2/BL31) + OP-TEE (BL32) + U-Boot (BL33) boot chain - SD card boot support Vendor kernel modules (pending): Nuvoton provides closed-source Verisilicon licensed drivers: - dcultrafb.ko (DCUltra display controller) - ma35d1-vc8000.ko (H.264 video codec) - galcore.ko (GPU driver) These modules require exact kernel vermagic match: 5.10.140-vendor-nuvoton-ma35d1 SMP mod_unload aarch64 Nuvoton is preparing custom builds of these modules for Armbian. Signed-off-by: TuAFBogey <uguvenen@gmail.com> | 7 个月前 | |
qemu-uboot-{arm64|x86}: bump to u-boot 2025.10-rc4 - rebase x86 patches | 10 个月前 | |
Add support for Arduino UNO Q (Qualcomm QRB2210) (#9623) * add support for arduino-uno-q * arduino-uno-q: fix boot with boot.scr and correct memory addresses ABL overwrites kernel_addr_r/fdt_addr_r/ramdisk_addr_r at runtime, causing memory overlap that corrupts the kernel Image header. Switch from extlinux to boot.scr which sets correct addresses in the 0xC0000000 RAM bank before loading kernel, initrd and dtb. U-Boot env loads boot.scr from partition 0x43 (GPT 67 "efi") with sysboot as fallback. * arduino-uno-q: update board and family config - Use boot.scr instead of extlinux (BOOTSCRIPT/BOOTENV_FILE in family) - Add SERIALCON=ttyMSM0 for serial console - BOOTSIZE=512 to fit kernel + initrd - Remove BOARD_FIRMWARE_INSTALL="-full", copy only needed firmware - Add WiFi ath10k firmware copy - Add ADB daemon with Armbian branding - Add first-boot rootfs resize service - Update kernel to 6.19.0 from qcom-v6.19.0-unoq branch * arduino-uno-q: fix image-output extension Use dd with sector offsets instead of loop device partitions to extract boot and rootfs images. The previous approach failed because the build framework releases the loop device before the extension runs. * arduino-uno-q: add first-boot rootfs resize for eMMC Add systemd service that expands the rootfs partition to fill the entire eMMC on first boot using sgdisk. Removes the empty userdata partition and recreates rootfs with all remaining space. * arduino-uno-q: update ath10k WiFi firmware to upstream Update board-2.bin from linux-firmware (ath-20260204) with support for additional board IDs. * arduino-uno-q: update kernel config for 6.19 * arduino-uno-q: revert board-2.bin to original version Restore the ath10k board-2.bin firmware to the version provided in the original board bring-up, as the upstream version has not been validated on this hardware. * arduino-uno-q: move flash binaries to armbian/qcombin Move EDL flash binaries (ABL, XBL, TrustZone, GPT tables, etc.) from packages/blobs/arduino/flash/ to the external armbian/qcombin repository under the Agatti folder, following the same pattern as rkbin for Rockchip and mtkbin for MediaTek. Add qcombin.sh extension to fetch binaries during build. Update image-output-arduino.sh to source flash files from qcombin cache and derive U-Boot package path from BRANCH/BOARD variables. * arduino-uno-q: add BOARD_VENDOR * arduino-uno-q: update qcombin path to Agatti/arduino-uno-q * arduino-uno-q: move firmware to armbian/firmware, rename boot script Move firmware blobs to armbian/firmware repository (armbian/firmware#123) and remove manual firmware copies from post_family_tweaks. Firmware is now installed via the armbian-firmware package. Rename boot-qcom to boot-qrb2210 to be family-specific. * arduino-uno-q: include prog_firehose_ddr.elf from Agatti root * arduino-uno-q: add qbootctl to prevent fastboot fallback --------- Co-authored-by: Hsun Lai <i@chainsx.cn> | 4 个月前 | |
station-m2: update u-boot patches | 2 年前 | |
rockchip64/rk3328: U-Boot v2022.04/07 add setexpr - aimed at nanopi-r2s and nanopineo3 - impacts: - boards (re)using 'nanopi-r2s-rk3328_defconfig' (rk3328) and: - boards using U-Boot v2022.04 or - boards using U-Boot v2022.07 - added explicit dependency on python3-setuptools as (at least) U-Boot v2022.04 and v2022.07 fail building due to missing 'distutils' for boards that use U-Boot v2022.04 or v2022.07 | 1 年前 | |
mkspi: u-boot 2026.04 migration (cherry picked from commit 1c07dda96640fe8a6e75233457f9424ca9d99795) | 1 个月前 | |
Add Milk-V DuoS, an aarch64+riscv64 board (#10326) * Add Milk-V DuoS, an aarch64+riscv64 board * sophgo-sg200x: give our own patches real authorship headers The 34 patches written for this port carried the placeholder header the autopatcher emits - "From: Armbian <info@armbian.com>" over a made-up Date - which says nothing about who wrote them or when. Review asked for something meaningful. Each now names its real author and carries the date of the commit that last changed that patch's content on the development branch, so the header matches the history the patch actually has. Where a patch was revised after it was first written - 0044 and 0052/0053 for the DT changes, 0046 for the regenerated comment - the date is that of the revision, not the original. The all-zero commit hash on the first line stays: these patches have no upstream commit to point at, and that is what the rest of the tree uses to say so. Header lines only; no patch payload was touched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: header the arm64 patches that had none Ten patches went in as bare diffs - no From, no Date, no Subject, just a blank line and the payload. They are the arm64 counterparts of 0040/0042/0044/0046/ 0048, written in the same commits as their riscv twins and touching only files this port creates, so they are ours to sign. Each now carries the same header its twin does, dated to the commit that last changed it - which for 0045 and 0047 is the commit that revised the pair, so the two architectures stay in step. The body is one line pointing at the riscv twin rather than a copy of its reasoning; the same change against the other DTS does not need the argument made twice. The two aic8800 patches had a real author but a placeholder Date of midnight UTC; they now carry the date they were written. Header lines only; no patch payload was touched. Every patch in this series now has a From, a Date and a Subject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: cut the comment wall in the family include Review asked for the absolute minimum here, and it was fair: 515 of the file's 988 lines were comment, several blocks running twenty or thirty lines to argue a case rather than state one. What is left says what each line does, and nothing else. Where a value looks arbitrary the comment names the constraint behind it - boot.cmd rather than boot.scr, CHIP_ARCH through the environment, "riscv" rather than "riscv64" - in a clause, not a paragraph. The reasoning that was dropped is not lost; it belongs in the port documentation rather than in a config file. 135 comment lines remain, down from 515, and the file is 607 lines rather than 988. Comments only: stripping comments and blank lines from this revision and from the original gives identical files. shfmt and bash -n are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * board: cut the Milk-V Duo S configs to the house format The first line of a board config is a one-line hardware description and nothing else. These carried a twelve-line preamble explaining the two-core split, the slide switch and how to read the boot log, plus a link to the vendor page. Both are now a single line in the form the rest of config/boards uses, with the core naming the only difference between them. The explanation of why one board ships as two configs is a thing to write down once, not in both files. * sophgo-sg200x: follow the tree's release candidate pin The bleedingedge branch pinned KERNELBRANCH to tag:v7.2-rc5 locally. That is the tree's decision, not a family's: config/sources/common.conf only calls the mainline_kernel_decide_version hooks when KERNELBRANCH is still empty, so the local pin suppressed the whole chain in mainline-kernel.conf.sh - including the hook that points KERNELSOURCE at Linus's tree when the stable mirrors have not caught up with the tag yet. Dropping it lets this family track the global pin, which is bumped weekly, instead of sitting on whichever candidate happened to be current the day it was written. * trim family config comments * remove nonexistent package removal from board configs * move kernel_comp_addr_r to 0x88000000 * implement a better fip.bin size guard. Unlikely to ever be needed * address Rabbit's concern * address Rabbit's concerns about USB gadget * fix btrfs potential failure * address the easy nitpick comments * reorder board family lines * Changes to the Bluetooth service addressing Rabbit's concerns * move the Duo S Bluetooth extension to a proper directory * address more of Rabbit's concerns about size | 25 天前 | |
Create 0001-orangepi4pro-pcie-3v3-dc1sw1.patch On Orange Pi 4 Pro, U-Boot fails to detect NVMe drives because it enables the wrong 3.3V regulator. The M.2 slot is powered by dc1sw1, but board-uboot.dts references dc1sw2. As a result, PCIe link training never starts (Link up timeout, LTSSM stays in Detect.Quiet), and nvme scan returns nothing. Linux works because its device tree marks both dc1sw1 and dc1sw2 as regulator-always-on, hiding the issue in U-Boot. This patch changes pcie3v3_supply to dc1sw1 and also corrects pcie1v8_supply to bldo1, aligning with the actual board schematic. | 7 天前 | |
Fix patch and compilation failures in crust support patch | 2 年前 | |
replace patch From: headers across the framework with something meaningful | 15 天前 | |
boards: add u-boot pieces for MBa93xxCA (image format, mkimage) Bump imx8m BOOTBRANCH, extend LEGACY_IMAGE_FORMAT to the new tqma93xx_mba93xxca defconfigs, and add CONFIG_IMX_CONFIG so Armbian's older mkimage can produce a flash.bin for MBa93xxCA instead of falling back to the unsupported cfgout IMAGE_VERSION 2 auto-generation. Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com> | 3 天前 | |
Add support for XpressReal T3 XpressReal(https://xpressreal.io/) is a family of Single Board Computers developed in collaboration between Fyde Innovations, Radxa and Realtek. XpressReal T3 is the first product in the family - a small form factor high performance single board computer powered by the Realtek RTD1619B, which runs FydeOS/openFyde and Linux! Now we are adding the awesome Armbian Linux support for XpressReal T3! This commit introduces some binary files that XpressReal T3 needed: - firmware/realtek/rtd1619b These binaries are the firmware for rtd1619b peripherals (including the audio decoder, video decoder, etc.). - u-boot-fw.tar.gz This contains some co-processor firmware, which needs to be loaded by u-boot in the early stage of boot. - u-boot-prebuilt.tar.gz These are hwsettings related files, used for tasks such as DDR initialization. These files come from the rtd1619b SDK, which has already been open-sourced on our github: - [firmware](https://github.com/XpressReal/linux-sdk/tree/main/meta-xpressreal/recipes-kernel/linux-firmware/files/rtd1619b) - [u-boot prebuilts](https://github.com/XpressReal/linux-sdk/tree/main/meta-xpressreal/recipes-bsp/u-boot/files/prebuilt/rtd1619b) | 11 个月前 | |
Move all legacy u-boot patches under one general legacy folder (#4386) * Move all legacy u-boot patches under one general legacy folder * Move 32b Rockchip under 2022.04 and legacy for Miqi Tested * Move Rock 3A patch dir under legacy * Move / merge meson64 patch folder into v2022.07 Merge 2022.04 (mainly Rockchip 32) into 2022.07, tested * Remove not needed patch * Add last kernel version to config | 3 年前 | |
uboot: Use semantic versioning for 2022.04 and 2022.07 Setuptools >66 only allows for semantic versioning, but old U-Boot versions don't use semver yet. This makes compilation fail with an error. | 2 年前 | |
odroidn2: u-boot: bump to v2026.04 (final) - remove left-behind 22.10 patch from previous bump | 4 个月前 | |
odroidhc4: bump to u-boot v2024.04; drop most defconfig patches in favor of hooks - add `pre_config_uboot_target` hook for switching BOOTCONFIG across the two targets - adapt `UBOOT_TARGET_MAP` to not call the defconfig Makefile targets directly, instead, just do a variable assignment (ignored by Make) - otherwise, when using the defconfig directly in the `UBOOT_TARGET_MAP`, the `post_config_uboot_target` .config changes are overwritten when Make is called - only patch left is boot usb-nvme-scsi/sata first (still done in meson64.h) - remove FIP handling from family file `meson-sm1.conf` into board file hook where it belongs - u-boot: enable more compression methods, EFI debugging, i2c, leds, tcp networking - use flashcp for mtd writing - Unchanged: - confirmed as of v2024.04: using the C4 (not HC4) defconfig is still needed to be able to write to mtd when booted from SD - also confirmed: one still needs to erase Petitboot using Petitboot, then boot from SD, to be able to flash mainline u-boot to mtd | 2 年前 | |
BananaPi CM4/M2S: `Delete old u-boot patches` Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 1 年前 | |
radxa-zero2: bump to u-boot 2024.07 (from 2023.10) - (confirmed by testing on-device) fixes UMS/Gadget stuff by including https://github.com/u-boot/u-boot/commit/4005729c0de234ffcf36465f6471755617b42375 that landed in v2024.01 | 1 年前 | |
nanopik2-s905: bump u-boot to v2026.04, move eMMC patch Advance the NanoPi K2 (Amlogic S905) bootloader from v2024.01 to the latest stable u-boot v2026.04. Move the board patch folder to the new version and rebase the eMMC-enable patch onto the relocated device tree: in v2026.04 the DTS moved from arch/arm/dts/ to the synced dts/upstream/ tree. The eMMC node content is unchanged; verified the patch applies (patch --dry-run / git apply --check) and nanopi-k2_defconfig still exists upstream. This also fixes the random MAC address bug: the older u-boot generated a new random ethernet MAC on every boot, so the board appeared as a different device each time. The newer u-boot derives a stable MAC, giving a consistent address across reboots. Tested on hardware (NanoPi K2): boots from eMMC and keeps a stable MAC across reboots. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 2 个月前 | |
turing-rk1: bump u-boot v2024.04 -> v2026.07 (fixes SWIG 4.3 build break on trixie) The v2024.04 build fails on Debian trixie because its shipped pylibfdt SWIG interface calls the 2-argument SWIG_Python_AppendOutput(), whose signature changed in SWIG 4.3.0 (trixie ships >= 4.3): scripts/dtc/pylibfdt/libfdt_wrap.c: error: too few arguments to function 'SWIG_Python_AppendOutput' v2026.07's libfdt.i_shipped uses the version-agnostic SWIG_AppendOutput() macro, so the host tool compiles cleanly. Both board patches are dropped as upstreamed in v2026.07: - 0001 define-boot-targets: mainline turing-rk1 header no longer uses the BOOT_TARGETS macro (moved to bootstd); patch is dead. - 0002 pcie3x4 clkreq: upstream DT already has pinctrl-0 = <&pcie3_reset>, <&pcie30x4m1_clkreqn>, <&pcie30x4m1_waken>. The board rides the generic v2026.07 patch dir; defconfig turing-rk1-rk3588_defconfig and the DT are both present upstream. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 1 个月前 | |
mt7623: revive Banana Pi R2 (u-boot 2026.07, kernel 6.18 + edge 7.1) Bring the MT7623n Banana Pi R2 back onto the current Armbian toolchain and mainline kernels, dormant since the 2024 CSC bring-up. u-boot / boot: - bump boot sources to v2026.07 (mainline) and rebase the board's enable-boot-from-ext4 patch onto it (defconfig tail + mt7623.h env). - eMMC boot is a known limitation: modern mainline u-boot boots from SD but hangs in early board_init_f on eMMC. v2024.07 and v2026.07 fail identically while only the old vendor u-boot ever booted eMMC, so it's a toolchain/ build-env difference, not a u-boot regression. SD is the supported path. kernel: - current -> 6.18 (was 6.6); add a new edge -> 7.1 target. - enable CONFIG_PINCTRL_MT2701: the mt7623 pinctrl DT node binds this driver; without it the board hangs after "clk: Disabling unused clocks". networking: - drop the pre-baked bridge/br0 preconfig; let users configure the DSA switch. - match bare 'wan'/'lan' DSA port names (not just wanX/lanX) in the default networkd netplan so the switch ports get DHCP out of the box. Verified on hardware: wan + lan0 both lease, routable, gateway/internet/DNS ok. board: - add current+edge targets and adopt igorpecovnik as maintainer. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 12 天前 | |
Orange Pi 3B: Update config Changes: - Bump U-Boot to v2026.01 - Add "current" option to kernel target - Simplify U-Boot processes | 6 个月前 | |
Feat/add tanix tx6s axp313 (#10290) * TX6s AXP313 board port + WiFi pwrseq/compatible fixes * Rename board config to .tvb classification for TV box * wifi: drop host-wake interrupt from wlan node The host-wake GPIO/interrupt config (PG15, edge-rising) was copied from an AP6330-pattern reference board. This board's actual WiFi chip is XR819 (xradio_wlan), not AP6330/brcmfmac. WiFi connects and passes traffic correctly without claiming this interrupt, and host-wake is only relevant for WoWLAN suspend, not basic connectivity, so it's safer to leave unclaimed until confirmed correct for this variant. * fix: enable SPDIF controller in axp313 DTS sound-spdif card was defined but the &spdif controller itself was never enabled, so the audio card couldn't bind. Add the missing &spdif { status = "okay"; }; override, matching the standard (non-axp313) TX6s variant. * Update maintainer for Tanix TX6s AXP313 board * fix: remove conflicting R_I2C PMIC node from tanix-tx6s defconfig axp305_1 under &r_i2c was a dummy placeholder (its own comment says 'appease the driver for now') with no real regulator config and a fake interrupt. The actual PMIC config lives under &r_rsb (axp305), which already provides all real regulators. R_I2C and R_RSB share the same physical pins (PL0/PL1) and can't both be enabled, so the dummy &r_i2c block was a real pinmux conflict. * fix: PR review round 1 (MAC, symlink, R_I2C conflict, maintainer) - Remove hardcoded WiFi MAC address from wlan node (all 3 kernel versions) to avoid address collisions across boards - Remove AP6330 firmware symlink; board's actual chip is XR819 - Set BOARD_MAINTAINER - Replace duplicate cp -R with install -Dm755 for audio config - Remove conflicting &r_i2c/axp305_1 dummy PMIC node from tanix-tx6s defconfig; real PMIC config is under &r_rsb/axp305 * fix: correct DRAM config namespace in axp313 defconfig CONFIG_SUNXI_DRAM_H616_DDR3_1333=y expects DRAM tuning values under the CONFIG_DRAM_SUN50I_H616_* namespace (matching tanix_tx6s_defconfig), but the axp313 defconfig had them under the wrong CONFIG_DRAM_SUNXI_* namespace. Kconfig was silently discarding these vendor-tuned DRAM timings and falling back to defaults instead. * fix: correct ethernet-phy node unit-address to match reg value DT convention requires the node's @unit-address suffix to match the reg property value in hex. reg = <16> is 0x10 in hex, so the node was renamed from ethernet-phy@16 to ethernet-phy@10 to match. The actual PHY address (reg = <16>) is unchanged. * fix: give axp313 variant a distinct compatible string Both the standard TX6s (AXP305) and TX6s AXP313 variant shared the identical compatible = "tanix,tx6s", "allwinner,sun50i-h616" string, making them indistinguishable to anything matching on compatible. Added a distinct primary compatible ("tanix,tx6s-axp313") for the AXP313 variant while keeping the shared fallbacks, updated consistently across the U-Boot defconfig and all 3 kernel DTS patch versions. * fix: add missing startup-delay-us to WiFi regulator on AXP305 variant The AXP313 variant's WiFi power regulator (reg_vcc_wifi) had startup-delay-us = <200000> to give the WiFi chip time to settle after WL_REG_ON goes high before SDIO probes it. The standard AXP305 variant was missing this delay entirely despite using the identical WiFi chip and power sequencing. Added for consistency and to avoid the same SDIO probe-timing issue across all 3 kernel versions. * revert: restore correct DRAM_SUNXI_* Kconfig namespace in axp313 defconfig An earlier commit changed these DRAM tuning symbols from CONFIG_DRAM_SUNXI_* to CONFIG_DRAM_SUN50I_H616_*, based on a mistaken comparison against the naming used in the standard tanix_tx6s_defconfig. Verified against this U-Boot version's actual Kconfig (arch/arm/mach-sunxi/Kconfig): DRAM_SUN50I_H616 is only the top-level enable symbol; the individual DRAM tuning parameters underneath it (DX_ODT, DX_DRI, CA_DRI, ODT_EN, TPR0/2/ 10/11/12, etc.) are genuinely namespaced DRAM_SUNXI_*. The previous change caused Kconfig to reject the values as invalid symbols and drop into an interactive reconfigure prompt, hanging non-interactive builds. Confirmed fixed with a full clean build. * fix: remove stale AIC8800 patch reference from sunxi-7.0 series.conf series.conf referenced patches.armbian/3401-net-wireless-backport-aic8800-sdio-v2025_0926_91c9dae5-mm2.patch, which doesn't exist anywhere in the tree. This would break kernel patch application for anyone building the sunxi-7.0 branch. * fix: correct indentation and remove stale patch references per review - Fix series.conf indentation for 0110-...ap6330-firmware.patch in sunxi-6.18 and sunxi-7.0 (spaces -> tab, matching surrounding lines) - Remove stale disabled references to patches.backports/32-pinctrl-sunxi-a523-Remove_unneeded_IRQ_remuxing_flag.patch and patches.backports/33-arm64-dts-allwinner-a523-Add_missing_GPIO_interrupt.patch from sunxi-6.18/series.conf. These were disabled with a leading '-' earlier to unblock the build (unrelated to this board), but upstream has since fully deleted both patch files and their series.conf entries, so these leftover references pointed to nothing. * refactor: move axp313 DTS to dt_64 folder (sunxi-6.18) Per review feedback, plain device trees that don't modify any existing upstream file can go directly in dt_64/ instead of being wrapped in a null-patch. Moved sun50i-h616-tanix-tx6s-axp313.dts there and removed the now-redundant 0646 patch and its series.conf entry. Confirmed with a clean build that the DTB still gets picked up and compiles correctly with no separate Makefile patch needed. * refactor: move standard TX6s DTS to dt_64 folder (sunxi-6.18) Same as the axp313 variant: 0645 only created a new file and never modified anything upstream, so per review feedback it's now a plain .dts in dt_64/ instead of a wrapped null-patch. Removed the 0645 patch and its series.conf entry. Confirmed with a clean build that both TX6s variants' DTBs still compile correctly together. * fix: align DRAM Kconfig namespace across all TX6s U-Boot defconfigs CodeRabbit flagged an inconsistency between 0010/0011/0012's DRAM tuning symbols. Verified against this U-Boot version's actual Kconfig (arch/arm/mach-sunxi/Kconfig): the real namespace for these DRAM tuning parameters is CONFIG_DRAM_SUNXI_*, not CONFIG_DRAM_SUN50I_H616_* (that's only the top-level DRAM_SUN50I_H616 enable symbol). This was confirmed empirically: 0011 briefly used the SUN50I_H616_* namespace and caused Kconfig to reject the values and hang on an interactive reconfigure prompt during a non-interactive build. Aligned 0010 and 0012 to the same DRAM_SUNXI_* namespace 0011 already uses, since 0011 is the one actually build-tested for this PR. * refactor: move TX6s DTS to dt_64 folder (sunxi-6.12, sunxi-7.0) Completes the dt_64 migration started for sunxi-6.18. Both variants' DTS content moved to plain .dts files under dt_64/, and 0645/0646 patches plus their series.conf entries removed for both kernel versions. Also caught and fixed the same WiFi host-wake interrupt issue in sunxi-6.12's axp313 DTS that was already fixed in sunxi-6.18 but never carried over here (sunxi-7.0 was already consistent). Confirmed with a clean full rebuild. * remove: armbian-audio-config script Per maintainer feedback, this script's scope and provenance were unclear for this PR - it targets multiple boards/families, not just this one, and its placement under h618 blobs read as more official than warranted. Confirmed by testing that audio works correctly without it; the only issue was selecting the right PulseAudio output (board has 3 stereo outputs: analog, HDMI, SPDIF). A properly scoped version can be proposed separately later if needed. * fix: remove stale WiFi host-wake interrupt from standard TX6s variant CodeRabbit correctly caught that the earlier host-wake interrupt removal only applied to the axp313 variant's wlan node - the standard (AXP305) TX6s variant still had interrupt-parent, interrupts, and interrupt-names in its wlan node across all three kernel versions, now migrated to dt_64/sun50i-h616-tanix-tx6s.dts. Removed for consistency with the axp313 variant, since this board family's actual WiFi chip doesn't correctly drive PG15 as host-wake. Confirmed with a clean build. --------- Co-authored-by: alnahian2011 <214164097+alnahian2011@users.noreply.github.com> | 29 天前 | |
rockchip rk3566: h96-TVbox: bump to uboot v2026.04 | 3 个月前 | |
khadas-vim3: bump mainline u-boot to v2026.04, move boot-order patch Move BOOTBRANCH_BOARD/BOOTPATCHDIR from v2025.04 to v2026.04 (the tag other meson64 boards — odroidn2, nanopik2-s905 — already build on). The board's 'SD -> USB -> NVMe -> eMMC' boot-order patch (meson64-boot-usb-nvme-scsi-first) moves with it into patch/u-boot/v2026.04/board_khadas-vim3/; verified it still applies cleanly (the BOOT_TARGET_DEVICES block in meson64.h is unchanged at v2026.04). v2025.04 patch dir stays for sakurapi-rk3308b. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 2 个月前 | |
youyeetoo-r1-v3: bump mainline u-boot to v2026.04 Move the board off the local v2025.10 patch chain to v2026.04. The two staging patches (defconfig + upstream dts) apply unchanged on the new base; the v2025.10 board patch dir is dropped. Signed-off-by: SuperKali <hello@superkali.me> | 1 个月前 | |
Restore the the E52C-specific reopen-disabled-nodes-for-rk3582 patch against v2026.01 | 3 天前 | |
replace patch From: headers across the framework with something meaningful | 15 天前 | |
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 个月前 | |
mvebu64: bump EspressoBin u-boot v2026.04 -> v2026.07 Move to the current u-boot release. Both mvebu64 patches still apply cleanly to v2026.07 (verified): the armada-37xx pinctrl boot-crash fix is still needed (the bug remains unfixed upstream) and the hardware-RNG defconfig addition. Rename the dedicated patchdir accordingly. ATF (v2.14.0) and the pinned A3720 blobs are unaffected by the u-boot version. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 1 个月前 | |
Updated kwiboo patches for RK3506 u-boot mainline Tested on: - ebyte-ecb41-pge - luckfox-lyra-zero-w | 10 天前 | |
sunxi64 (64-bit): bump u-boot v2024.01 -> v2026.07-rc4 The sun50i family (sunxi64_common.inc; A64/H5/H6/H616/H618) is on u-boot v2024.01, which hits the same trixie SWIG 4.3 / pylibfdt build break as the 32-bit family. Move the family default to v2026.07-rc4 with a fresh v2026.07-sunxi64 patchdir, re-adding board patches as confirmed (bigtreetech-cb1, orangepi3-lts standalone u-boot with ethernet restored, orangepi-win USB-VBUS, recore, nanopi k1plus / neo-core2, inovato-quadra; cherryba-m1 moved off its half-broken v2025.04 self-pin). crust boards (orangepiprime, nanopineo2, ...) switch to native SCP, dropping the legacy crust u-boot patches. Boards self-pinning a newer BOOTBRANCH keep their pins. Migration kickoff for the 64-bit half; per-board build/boot status in the PR description. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 2 个月前 | |
replace patch From: headers across the framework with something meaningful | 15 天前 | |
replace patch From: headers across the framework with something meaningful | 15 天前 | |
Revert "radxa-e52c: bump uboot to v2026.07" This reverts commit e0732862cce6f9025306546ec23995f66cd7a26f. | 3 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 14 天前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 25 天前 | ||
| 15 天前 | ||
| 7 天前 | ||
| 7 个月前 | ||
| 10 个月前 | ||
| 4 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 个月前 | ||
| 25 天前 | ||
| 7 天前 | ||
| 2 年前 | ||
| 15 天前 | ||
| 3 天前 | ||
| 11 个月前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 4 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 12 天前 | ||
| 6 个月前 | ||
| 29 天前 | ||
| 3 个月前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 3 天前 | ||
| 15 天前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 10 天前 | ||
| 2 个月前 | ||
| 15 天前 | ||
| 15 天前 | ||
| 3 天前 |