| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
meson8, MXQ: add boot from usb support, configurable dtb | 1 年前 | |
cubox-i: default console to both (HDMI + serial) Change boot-cubox.cmd default console "display" -> "both" so cubox-i ships with serial console enabled out of the box (kernel messages + login on both HDMI tty1 and ttymxc0 serial). Useful for a board frequently run headless; HDMI still shows everything. Overridable via console= in armbianEnv.txt. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 2 个月前 | |
allow booting off more than first partition with distroboot (#3977) | 4 年前 | |
Enable bootscript templating - Enable bootscript templating using `envsubst`. - Add generic bootscript. - Fix: `test` does not support `==`, but deceptively returns `true` in case you use it. - De-duplicate kernel commandline console options. | 9 个月前 | |
Generic bootscript template Some background. How to use it. | 9 个月前 | |
boot-genio: load kernel above reserved low-RAM hole, guard failed loads The kernel load failed on NIO-12L with: Loading kernel image to 0x40000000... ** Reading file would overwrite reserved memory ** Failed to load '/boot/Image' then booted garbage at 0x40000000 ("Bad Linux ARM64 Image magic!"), because the script didn't check the load return code. Root cause is a layout thinko. The script reserved kernel_addr_r at 0x40000000 with a comment claiming a 100 MB window (0x40000000-0x46400000), but the board's first reserved region, low RAM 0x43200000-0x43DFFFFF, sits *inside* that claimed window. Only the first 50 MB is actually contiguous: 0x43200000 - 0x40000000 = 0x3200000 = 52,428,800 bytes = 50 MB The kernel Image is 54,565,376 bytes (~52.04 MB), so loading it at 0x40000000 would end at 0x43409A00 -- ~2.04 MB into the reserved region. U-Boot's LMB check refuses the write, the (previously unchecked) load fails, and booti runs whatever stale data is at 0x40000000. Move kernel_addr_r above the hole to 0x44000000 (2 MB aligned, just past the region's end at 0x43DFFFFF). That gives a contiguous window up to the next reserved region at 0x54600000: 0x54600000 - 0x44000000 = 0x10600000 = 262 MB The 52 MB kernel now lands at 0x44000000-0x47409A00 with ~210 MB of headroom, clear of fdt (0x56000000) and ramdisk (0x64000000), which were already placed above the holes. Also guard the kernel/initramfs/dtb loads with if/else+exit so a refused load aborts loudly instead of silently falling through to booti on an unwritten address. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> | 2 个月前 | |
Fix cmdline fsck argument | 4 个月前 | |
K3: Update to latest U-Boot v2025.01 Now that upstream U-Boot has support for building K3 boot artifacts we can drop using the ti-u-boot fork. Switch to v2025.01 and adjust file names and add new dependencies as needed. | 1 年前 | |
imx8ulp: reduce ATF log level Set ATF_LOG_LEVEL=20 to silence BL31 SCMI/upower INFO spam, honor it in compile_atf, and hash ATF vars in uboot artifacts. Use quiet loglevel=4 in uEnv and lower the kernel default console loglevel to 4. | 2 个月前 | |
Changes to allow building for Macchiatobin and building modules necessary to operate mcbin hardware (#3784) * tf-a sources use mrvl_flash rather than 'all' target * add armada 8k ethernet and SFP cages for macchiatobin use * u-boot configuration for mcbin * fix bootscript for u-boot variables * separate ebin and mcbin with if statements * add a8k PCIe and CPUFreq drivers for macchiatobin | 4 年前 | |
Helios4: Add SPI bootloader install feature (#1126) * Helios4: Add workaround for SPI and SATA concurrent access issue Concurrent access on SPI NOR and SATA drives can lead to unstable SATA. Therefore as workaround, disable SATA controller when SPI flash access is needed and make it as user configurable item in armbianEnv.txt This workaround might applies to Clearfog too. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Helios4: Add U-Boot SPI Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Helios4: Add SPI bootloader install feature This will allow to use nand-sata-install to perform the following operations on Helios4 : - Install bootloader to SPI NOR Flash (Option 5 in Menu). - Copy RootFS to USB storage in order to boot from SPI with RootFS on USB (Option 6 in Menu). * Unmount temp mount points in create_armbian() instead of hardcoded /dev/sda | 7 年前 | |
bootscript: Remove deprecated bootarg "swapaccount=1" The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f | 2 年前 | |
config: bootscripts: Rename s4t7.cmd to boot-meson-s4t7-legacy.cmd Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 23 天前 | |
Fixup serial in boot-meson-s4t7.cmd file Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 23 天前 | |
bootscript: Remove deprecated bootarg "swapaccount=1" The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f | 2 年前 | |
Bananapi R2 (#1151) * Initial commit BPi R2: Currently working/not working: - u-boot: - builds with minor issues - patching and cleanup happens on 'https://github.com/chwe17/u-boot-mt' - next (https://github.com/frank-w/BPI-R2-4.14) - boots with minor issues - ETH doesn't work with nm - sata works - no wifi (needs driver from: https://github.com/frank-w/BPI-R2-4.4) - USB not working (xhci-mtk 1a1c0000.usb: fail to get vbus) needs investigation - appended device tree is needed due to u-boot doesn't work with fdt (kernelpacking needs adjustemts e.g. cat zImage dtb > zImage-dtb - dev (kernel.org master) - untested, needs adjustments in config (e.g. CONFIG_LOCALVERSION="") - since no defconfig is available config is based on frank-w 4.16 Kernel - Kernel builds without issues - manual packing of kernel and dtb similar to next The board boots, serial console is available but everything else must be expected as not working! - to do: - u-boot needs a cleanup - binary blobs needs investigation - eMMC is **not tested** and needs for sure adjustements! (don't try nand-sata-install!!!) - bootscript isn't tested (only manual boot over u-boot console at the moment) - both kernelconfigs aren't 'armbian standard' modules need to be adjusted Only use it when you know're familiar with u-boot commands! * Small fixes, add bootscript - add bootscript for patched u-boot (needs patching of u-boot, currently under investigation and not working properly) - revert cat zImage dtb > zImage-dtb (cause not working) - first cleanup of dev kernelconfig (remove CONFIG_LOCALVERSION="") * Minor fixup -kernelconfig for next was adjustet so that USB is recognized -firt bootscripts was written to boot with source command (doesn't work 100% reliable) -slightly adjustd boardconfig (e.g. bootscript) must still be considered as early wip! * small update (FDT works now) -working bootscript -adjusted boardconfig -earlyprintk activated in kernelconfig * First attempt to get ETH working -all interfaces are bridged together -performance sucks at the moment (not clear if it's related to insane network configuration or I miss something obvious... :P ) * Major update (see below for changes): - 4.14 kernel was dropped due to https://forum.armbian.com/topic/7296-bananapi-r2-csc-mt7623-as-new-boardfamily/?do=findComment&comment=55194 and following - boot.cmd was adjusted to 'clean' mainline behaviour - next build opition and its defaultconfg was removed (at the moment dev only) - rework of the network default configuration - default configuration will be over network.d **not** NetworkManager - per default all wired interfaces are bridged together to br0 (still wip) - old 'interfaces' configuration was removed - boardconfig is adjusted (no desktop until I've prove that HDMI works) - what works/ not works: - board boots up without manual u-boot hacking - SATA, USB3 (massstorage) is tested and works without issues - due to rework of network configuration this is still wip and must be considered as 'not working' * moved to network.d for configuration of wired network - renamed bsp packages - blacklist wired interfaces for NetworkManager - defined all wired interfaces as br0 in systemd/network - defined networkd als default renderer for bionic (not tested yet!) * The houskeeping commit: - BOARDFAMILY was renamed to mt7623 instead of mt7623n (including patchfolders etc.) - Network.d has no fully control over wired networkes (block NM from controll, start networkd on firstrun etc.) - Further cleanup kernelconfig - CPU temp is visible from userspace - missed switch driver loaded - cryptodrivers are there (not tested) - still a bunch of work * Add DMA mem alloc patch -under testing! * Add next option (4.17.y) stick dev to master (4.18-rc1 untested) * minor fixes: - solve kconfig issues between 4.17 and 4.18 - stick next branch to 4.18 - first attempts to bring up gmac2 (doesn't work currently) * switch to upstream u-boot - fix ext4 dependency in patch series - kernelpacking currently broken * add bootz & cmd_ext4 * resolved merge conflict * apply ugly u-boot patch, fix bootscript * remove unneeded stuff, apply forgotten stuff * update config for dev & clean up boardconf (remove xenial) * - drop dev and next, move into default. There is no intention to provide stock kernel - fixed board description, renamed to WIP, where it can be merged later - packing boot firmware to the u-boot package - docker dependencies (aufs will be added later. not essential) - attached to 4.19.y - loading armbianEnv.txt - UUID support (tested) - enabled ZRAM (tested) - enabled eMMC install (not quite working properly yet) - Bionic has some issues with systemd networking. * gov to ondemand (thermals are conservative anyway), remove unneeded kernelconfigs * Added AUFS, remove debug from kernel boot parameters, add ath10 mPCI support (which works) * add power-off-key and rtc * Added onboard wireless, but it's enabling is disabled by default. Too fragile. * Change to CSC target | 7 年前 | |
boards / Helios4: Fix: libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Bump U-Boot v2025.10: - In DT path `/soc/spi@10680/` the entry `spi-flash@0` was renamed to `flash@0` | 9 个月前 | |
fix: address review comments - Rename board config to .csc (no maintainer) - Remove duplicate board name from comment - Change verbosity from 7 to 1 (default) - Remove ATF patch, use ATF_SKIP_LDFLAGS_WL instead - Move CONFIG_RD_* to kernel config (fix artifact caching) - Fix networking comment (chrony -> NetworkManager) - Replace -j12 with -j8 - Add fdt addr/resize after DTB reload on overlay error | 8 个月前 | |
Update boot-odroid-c1.ini -Clean, remove params for old kernel -Add option to disable usb autosuspend -Add display console | 2 年前 | |
Support Plymouth (#4133) * Add plymouth-theme-armbian package * Adjust all bootscripts to adapt plymouth * Auto show logo accroding to BOOT_LOGO * Enable plymouth detail mode when bootlogo=false * Add a new board config var - HAS_VIDEO_OUTPUT This var is used to indicate whether device has a HW video output. If it's set to "no", we will disable kernel bootsplash, plymouth and BUILD_DESKTOP * Rename package to be aligned with others * Disable kernel bootloader, but keep the code for it * Rather keep bootlogo in the kernel for a while, otherwise kernel upgrade will turn bootup into the darkness Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> Co-authored-by: Igor <igor@armbian.com> | 3 年前 | |
Support Plymouth (#4133) * Add plymouth-theme-armbian package * Adjust all bootscripts to adapt plymouth * Auto show logo accroding to BOOT_LOGO * Enable plymouth detail mode when bootlogo=false * Add a new board config var - HAS_VIDEO_OUTPUT This var is used to indicate whether device has a HW video output. If it's set to "no", we will disable kernel bootsplash, plymouth and BUILD_DESKTOP * Rename package to be aligned with others * Disable kernel bootloader, but keep the code for it * Rather keep bootlogo in the kernel for a while, otherwise kernel upgrade will turn bootup into the darkness Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> Co-authored-by: Igor <igor@armbian.com> | 3 年前 | |
fix: cloudshell2 dtbo overlay path in boot.ini Currently, dtbo path in boot.ini is wrong. So we cannot load device tree blob overlays for cloudshell2. This commit fix this path in boot.ini | 2 年前 | |
onecloud: Enable `Plymouth` (#4228) | 3 年前 | |
qemu arm64: bump u-boot and fix wrong boot script parameter Now it boots OOB: https://paste.armbian.com/ololipacam | 1 年前 | |
qemu-uboot-arm64/qemu-uboot-x86: split more x86/arm64 differences, add some docs, bump to u-boot 23.04 +update-patches; add arm64 bootscript | 3 年前 | |
Support Plymouth (#4133) * Add plymouth-theme-armbian package * Adjust all bootscripts to adapt plymouth * Auto show logo accroding to BOOT_LOGO * Enable plymouth detail mode when bootlogo=false * Add a new board config var - HAS_VIDEO_OUTPUT This var is used to indicate whether device has a HW video output. If it's set to "no", we will disable kernel bootsplash, plymouth and BUILD_DESKTOP * Rename package to be aligned with others * Disable kernel bootloader, but keep the code for it * Rather keep bootlogo in the kernel for a while, otherwise kernel upgrade will turn bootup into the darkness Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> Co-authored-by: Igor <igor@armbian.com> | 3 年前 | |
fix(boot-qrb2210): correct load address comment Update the comment for auxiliary load addresses to indicate that they must remain above 0x8a800000, where boot.scr is sourced from. Signed-off-by: Govind Singh <govind.sk85@gmail.com> | 3 个月前 | |
bootscript: Remove deprecated bootarg "swapaccount=1" The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f | 2 年前 | |
rockchip: Add CSC board Luckfox Lyra Plus | 10 个月前 | |
rockchip: rk3576: Fix serial console to use UART0 (ttyS0) (#8936) - Change debug console from ttyS2 to ttyS0 - Remove SERIALCON from board configs - Set console based on BOOT_SOC - Enable UART0 in device tree for nanopi-r76s | 9 个月前 | |
bootscript: rename boot-rk3588-legacy.cmd to boot-rk35xx.cmd | 1 年前 | |
bootscript: Remove deprecated bootarg "swapaccount=1" The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f | 2 年前 | |
Merged rock-s0 and rockpi-s boards fully into rockchip64 family (#7382) Also removed some obsolete board specific boot script tweaks | 1 年前 | |
Add board: Luckfox Nova (RK3308B) Compact RK3308B board: 512MB DDR3, 8GB eMMC, 100M Ethernet (RTL8201F), USB-C OTG peripheral, USB-A host, microSD. Debug console is UART4 at 1500000 baud. Fully mainline: U-Boot 2025.04 (binman, rkbin DDR/BL31) and mainline kernel for both current (6.18) and edge (7.0). Board quirks handled: - the microSD slot only has DAT0 usable - 4-bit transfers fail with a Start Bit Error in U-Boot and I/O errors in Linux (verified with two cards), so both the U-Boot and kernel DTS pin the slot to bus-width=1 (SD High Speed at 50MHz works fine). The U-Boot side also needs dwmci_setup_cfg() to honor a 1-bit DT bus-width plus two dw_mmc fixes backported from upstream (dwmci_control_clken CDONE ack, setup_bus same-frequency skip). - the evb_rk3308 download-key handler hardcodes the pre-DM "saradc" device name; fixed to the actual device name so the recovery key works, and the key now enters RockUSB directly (usable with rkdeveloptool/upgrade_tool without entering maskrom). - ethernet PHY is strapped at MDIO address 0; the gmac node lets stmmac scan the bus instead of assuming an address. Tested on hardware: boots from eMMC and SD (SD preferred when inserted), ethernet, USB host/OTG, PWM, SARADC, recovery key. | 2 个月前 | |
bootscript: Remove deprecated bootarg "swapaccount=1" The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f | 2 年前 | |
RV1106: Switch u-boot from extlinux to bootscript Switch u-boot autoboot method from extlinux to the typical Armbian bootscript. This is required in order to support devicetree overlays in this family. | 4 个月前 | |
Add board: EASY EAI Nano RV1126 | 2 个月前 | |
S5P6818 (NanoPC-T3+ / NanoPi M3 / Fire3): mainline 7.2 bring-up (#10674) * s5p6818: resurrect NanoPC-T3+ (nanopct3plus.eos) and its family Restore the Nexell S5P6818 support that was dropped after v24.05, so the NanoPC-T3+ builds on the current framework again. Brought back verbatim from origin/v24.05: - config/boards/nanopct3plus.eos - config/sources/families/s5p6818.conf (u-boot rafaello7/u-boot-nanopi-m3, kernel armbian/linux branch s5p6818 @ 4.14, custom NSIH boot.img build + 1G/2G BL1 blob selection) - config/kernel/linux-s5p6818-legacy.config - config/bootenv/s5p6818.txt, config/bootscripts/boot-s5p6818.cmd - patch/kernel/archive/s5p6818-4.14/* (+ the s5p6818-legacy compat symlink) - patch/u-boot/legacy/u-boot-s5p6818/* - packages/blobs/nanopi/{1g,2g}-bl1-nanopi.bin (required by the u-boot postprocess) Verified against current main: the family hooks (write_uboot_platform, uboot_custom_postprocess, family_tweaks) and the legacy/ u-boot patch-dir convention are still honoured; both upstream sources (the armbian/linux s5p6818 branch and the rafaello7 u-boot master) still exist and are fetchable; board + family confs pass bash -n. Kept as .eos (end-of-support), as it was. A full 4.14 kernel + legacy u-boot build with the current toolchain is the remaining validation. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add EDGE (mainline 7.2) kernel target for NanoPC-T3+ Bring the Nexell S5P6818 up on a mainline 7.2 kernel (legacy 4.14 kept untouched). Verified on a NanoPC-T3+: boots to an interactive ttySAC0 login under the existing 2016 fork u-boot - clean console, EXT4 rootfs mounts, systemd runs. Kernel (patch/kernel/archive/s5p6818-7.2, on top of mainline v7.2.4): - 0001: minimal nexell platform (Kconfig, DT, console + SD). - 0002: boot enablement - * finalise_el2: return early - the fork u-boot's EL2 handoff leaves the hvc trap broken and A53 nVHE needs no EL2 finalise (KVM, the other hvc user, is disabled in the config). * The ARM generic-timer PPIs are not delivered and the system counter (CNTVCT) is frozen by design on this SoC, so drive the kernel clockevent/clocksource from the Nexell PWM timer (samsung,s5p6440-pwm; ARCH_NEXELL selects CLKSRC_SAMSUNG_PWM), keep arm,armv8-timer counter-only so time_init() does not panic, and redirect arm64 get_cycles()/__delay() to the PWM so udelay() does not spin forever. * nexell,s5p6818-uart drvdata + uart fixed-clock at the real 50.688 MHz (u-boot UBRDIV=26/UDIVSLOT=8) so the console baud is correct. config/kernel/linux-s5p6818-edge.config: CONFIG_VIRTUALIZATION/KVM off. config/bootscripts/boot-s5p6818.cmd: kernel_addr_r 2 MiB aligned. config/sources/families/s5p6818.conf: edge branch = 7.2; NSIH postprocess no longer relies on xxd. board: KERNEL_TARGET="legacy,edge". u-boot v2026.07 port is included but still cold-boot unstable; the fork u-boot remains the working base for now. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add EDGE 7.2 peripheral support (GbE, SMP, USB, I2C, RTC, PWM, thermal) Consolidated, hardware-validated peripheral bring-up for the NanoPC-T3+ (Nexell S5P6818) on the mainline 7.2 kernel, as a clean per-subsystem patch series (0003-0012) on top of the boot bring-up (0001-0002): 0003 pinctrl/gpio 0008 i2c (s3c2410) 0004 clk (PLL+clkgen) 0009 rtc (rtc-nx) 0005 reset-simple 0010 pwm (samsung) 0006 smp tick bcast 0011 thermal (exynos_tmu) 0007 usb2 phy 0012 arm64 dts (all peripherals) Verified on hardware: 1GbE (DHCP+SSH), 8 cores stable, USB EHCI/OHCI/dwc2 + hub, I2C x3, RTC, PWM output, cpu-thermal ~51C. Kernel config enables the above; the mainline v2026.07 u-boot port stays marked incomplete (fork 2016.01 u-boot is the working bootloader). Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: complete peripheral series, switch to CURRENT kernel, add M3/Fire3 - Add the pwm (0010), thermal (0011) and DT (0012) patches that a bad glob dropped from the previous consolidation commit - without 0012 the branch had no peripheral DT at all. - Retire the 4.14 legacy kernel: the mainline 7.2 revival becomes the CURRENT (default) branch. Rename linux-s5p6818-edge.config -> -current.config, drop linux-s5p6818-legacy.config, simplify the family case to 'current' only. - One shared device tree boots the whole FriendlyARM S5P6818 family (NanoPi M3, Fire3, NanoPC-T3/T3+): identical peripherals, per-board RAM filled in by u-boot (ft_board_setup). Add nanopi-m3 and nanopi-fire3 board configs. - Add on-board green status LED (gpio_b-12, active low) with the heartbeat trigger by default. Signed-off-by: Igor Pecovnik <igor@armbian.com> * board: s5p6818: promote NanoPC-T3+/M3/Fire3 to supported (.conf), set maintainer Rename the three FriendlyARM S5P6818 boards from .eos/.csc to .conf (supported tier) now that the mainline 7.2 CURRENT kernel brings up all their peripherals, and set BOARD_MAINTAINER=igorpecovnik. Signed-off-by: Igor Pecovnik <igor@armbian.com> * board: s5p6818: single family target on the NanoPC-T3+ Keep one build target - the NanoPC-T3+ (the board on the bench) - as the reference for the whole FriendlyARM S5P6818 family. The same kernel + shared device tree also boot NanoPi M3 and Fire3 (u-boot supplies the per-board RAM size), so drop the separate nanopi-m3/nanopi-fire3 board configs and make the board name say it covers all three. Signed-off-by: Igor Pecovnik <igor@armbian.com> * board: s5p6818: fix nanopct3plus menu description (first comment line) The first comment line is what the board-selection menu shows; make it a concise one-liner naming the SoC and the covered boards instead of a wrapping sentence. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: rewrite kernel config to Armbian defconfig, drop 4.14 patches - rewrite-kernel-config: normalize linux-s5p6818-current.config to a minimal Armbian defconfig against the patched 7.2 tree. Verified nothing important to this SoC is lost - all driver symbols (pinctrl/clk/phy/gbe/usb/i2c/rtc/pwm/ thermal, LEDs) survive expansion, VIRTUALIZATION stays off (KVM broken on this SoC's EL2), console/SMP-broadcast/MMC/fs intact. The only dropped symbols were KVM deps (correct with virt off) and stale MDIO_BUS/MDIO_DEVICE symbols that no longer exist in 7.2 (MDIO now via PHYLIB+FWNODE_MDIO+OF_MDIO). - drop the retired 4.14 legacy kernel patches (archive/s5p6818-4.14 and the s5p6818-legacy link) now that the mainline 7.2 CURRENT kernel replaces them. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add software-reset restart handler (patch 0013 + config) Export the nexell-restart driver as kernel patch 0013 and enable CONFIG_POWER_RESET_NEXELL. Provides a CLKPWR software-reset restart handler that outranks the firmware PSCI reset, which returns less reliably on this SoC. Warm reboot remains best-effort on the fork boot chain (boot ROM self-refresh-exit is marginal); the reset button always recovers. Documented in the driver. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add audio (I2S + ES8316) and fix I2C/I2S reset + PLL clock Analog audio on the NanoPC-T3+/M3/Fire3 3.5mm jack: SoC I2S0 (master) -> ES8316 codec over the ARM PL080 DMA, via a ported Nexell I2S ASoC driver + generic dmaengine PCM + simple-audio-card. HW-verified: card registers, codec responds on I2C, mixer works, a 48kHz stream runs clean (DMA/I2S/ MCLK all good); only audibility needs a physical plug. Two prerequisite fixes uncovered during bring-up: - reset-simple had reset_us=0 for the Nexell controller, so reset_control_reset() was a no-op and the I2C (and I2S) blocks stayed held in reset from u-boot - every I2C transaction timed out. This is why I2C never actually transacted despite the bus registering. - the nexell clk driver looked up PLLs by the wrong clkdev name, so any clock deriving its rate from a PLL (the I2S MCLK) came out 0. Patches 0014-0017 + CONFIG_AMBA_PL08X / CONFIG_SND_SOC_NEXELL[_I2S]. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add eMMC + SDIO WiFi, stabilise mmc numbering Wire up the two remaining SD/MMC channels on the NanoPC-T3+/M3/Fire3: - eMMC on SDMMC2 (patch 0018): HW-verified, 14.6 GiB at 52 MHz (4-bit). - SDIO WiFi on SDMMC1 (patch 0019): Broadcom BCM43430 (brcmfmac). u-boot never powers SDMMC1, so this needed its pins muxed, its clk-gen gate enabled (new sdhc1 clk-critical clock) and its reset released. The chip enumerates as an SDIO card and brcmfmac binds + loads firmware (brcmfmac43430-sdio.*, from the rootfs, as with any brcmfmac board). Patch 0019 also pins the mmc host numbering via aliases so mmcblkN is stable now that a non-removable eMMC is present (it raced the polled SD for mmcblk0, breaking root=/dev/mmcblk0p1). Config: +BRCMFMAC_SDIO=y (BRCMFMAC/CFG80211/RFKILL already =m). Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add on-board Bluetooth (AP6212 / BCM43430 on UART1) Patch 0020 makes samsung_tty release an optional reset in probe; patch 0021 adds UART1 (@0xc00a0000) + the bluetooth serdev node. Like the WiFi side, u-boot never touches UART1, so it needs its clk-gen gate kept on (clk-critical) and its reset released. The BT chip is powered via BT_REG_ON (gpiob-8, moved off the WiFi pwrseq) and hci_uart/hci_bcm loads brcm/BCM43430A1.hcd (already in armbian/firmware). HW-verified on a NanoPC-T3+: hci0 comes up (BCM43430A1, BT4.0), firmware patchram loads, and an LE scan discovers nearby devices. No config change needed - BT=m selects CRYPTO_ECDH and the serdev/bcm bits are default/ selected; a full modules build ships them. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: build the working rafaello7 2016.01 u-boot (not mainline v2026.07) The mainline v2026.07 port reset-loops on a COLD boot (unresolved 2026-u-boot /GCC-15 early-env issue), so a framework image built with it does not boot the board reliably. Point BOOTSOURCE at the rafaello7 nanopi3 fork (tag v1.2, nanopim3_defconfig) - the known-good bootloader that boots this SoC cold+warm at EL2, and what actually runs on the hardware today. TEXT_BASE 0x43c00000 already matches the NSIH launch address, so the boot.img assembly hook is unchanged. The v2026.07 patch set stays in-tree for future work. Signed-off-by: Igor Pecovnik <igor@armbian.com> * nanopct3plus: add BOARD_VENDOR, fix BOOTCONFIG for the rafaello7 u-boot - BOARD_VENDOR="friendlyelec" (required board asset check; matches the other FriendlyELEC boards). - BOOTCONFIG "s5p6818_nanopim3_defconfig" -> "nanopim3_defconfig": the rafaello7 fork's actual defconfig name (the old name existed only in the v2026.07 port and would have failed the fork build). Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: ship prebuilt rafaello7 u-boot.bin (2016.01 won't build on modern host) The rafaello7 2016.01 fork is the known-good bootloader, but its host tools (fdtgrep/mkimage/... via lib/libfdt) fail to compile against a modern host libfdt-dev in Armbian's build container (redefinition of fdt64_t etc.), so a from-source build is not currently possible. Ship the upstream-released prebuilt binary instead (packages/blobs/nanopi/ uboot-nanopi3.bin = rafaello7 release v1.2, U-Boot 2016.01-gb915959), alongside the existing BL1 blobs. The u-boot source is still fetched+configured for versioning, but UBOOT_TARGET_MAP's make target is the no-op 'ubootversion' so nothing is compiled, and uboot_custom_postprocess assembles boot.img from NSIH + BL1 + the prebuilt u-boot.bin. TEXT_BASE 0x43c00000 matches the NSIH. Revisit a from-source build if the 2016.01 host-tools/libfdt issue is patched or the mainline v2026.07 cold-boot crash is fixed. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: ship the proven boot region blob (fixes non-booting framework image) A full framework image did not boot: both the BL1 blob and the u-boot we shipped (hand-assembled NSIH + rafaello7 v1.2 prebuilt) differed from the binaries that actually boot this board, so the ROM/2ndboot never came up. Replace the hand-assembly with the proven boot region captured verbatim from a known-good on-board install: BL1 + NSIH + "U-Boot 2016.01-armbian" (packages/blobs/nanopi/boot-nanopi3-2g.img, 2 GiB / NanoPC-T3+). The postprocess now just stamps the offset-0x50 boot-device selector (0=SD for boot.img, 2=eMMC for bootemmc.img); write_uboot_platform dd's it at sector 1. HW-verified: a framework Trixie image now boots to userspace + gigabit eth0. Also enable a visible console for this SoC: earlycon=s5pv210,mmio32,0xc00a1000 in the boot script (without it the board looks dead at "Starting kernel"), and bump default verbosity to 7 while the platform is in bring-up. The rafaello7 v1.2 prebuilt u-boot.bin is dropped (it differed and did not boot). TODO: capture a 1 GiB boot region for the M3/Fire3; build u-boot from source once the 2016.01 host-tools/libfdt or the v2026.07 cold-boot issue is fixed. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: split into 2 GiB (T3+) and 1 GiB (Fire3/M3/T3) images The only per-board difference is DRAM init, which lives in the BL1 inside the boot blob, so ship two proven boot regions and two board targets: - nanopct3plus: NanoPC-T3+ (2 GiB), boot-nanopi3-2g.img (from a T3+ eMMC). - nanopifire3: NanoPi Fire3 / M3 / NanoPC-T3 (1 GiB), boot-nanopi3-1g.img, captured from the last known good Armbian Fire3 image (21.02.1). The 1 GiB BL1 is byte-identical to the packaged 1g-bl1-nanopi.bin; the blob pairs it with the working "2016.01-armbian" u-boot. The family postprocess picks the blob by BOARD. Kernel + device tree are shared (u-boot writes the real RAM size into the DT). HW-verified: the 2 GiB image boots the T3+; the 1 GiB image is for the Fire3, which does not boot the 2 GiB BL1 (DRAM init mismatch), as expected. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: split board DT into common dtsi + per-board M3/Fire3 trees Add kernel patch 0022: the single s5p6818-nanopi-m3.dts described the whole FriendlyElec S5P6818 family, but the NanoPi Fire3 has no on-board eMMC, no SDIO WiFi/Bluetooth and no audio codec, so on it the ES8316 / simple-audio- card / SDIO host / BT serdev all fail to probe and spam the log. Split the tree: s5p6818-nanopi3-common.dtsi - peripherals every board has (UART, micro-SD, GbE PHY, I2C, PWM, status LED); board-specific blocks stay disabled. s5p6818-nanopi-m3.dts - full boards (M3, NanoPC-T3/T3+): + eMMC, SDIO WiFi, Bluetooth, ES8316 audio. s5p6818-nanopi-fire3.dts - Fire3: common only -> clean boot, no phantom peripheral nodes. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: select per-board DT via BOOT_FDT_FILE; add NanoPi M3 board Wire the DT split (patch 0022) through to the images. Each board .conf now sets BOOT_FDT_FILE, which the build writes as fdtfile= into armbianEnv.txt and the single boot-s5p6818.cmd imports: nanopct3plus (2 GiB) -> nexell/s5p6818-nanopi-m3.dtb (full) nanopim3 (1 GiB) -> nexell/s5p6818-nanopi-m3.dtb (full) [new board] nanopifire3 (1 GiB) -> nexell/s5p6818-nanopi-fire3.dtb (minimal) boot-s5p6818.cmd: load ${prefix}dtb/${fdtfile} (standard vendor/board scheme, fallback to the full m3 dtb) instead of the hard-coded nexell/ path and the bogus rev07 fallback. nanopifire3.conf narrowed to the Fire3 alone (was "Fire3/M3/T3"); NanoPi M3 / NanoPC-T3 split out into nanopim3.conf. Board image assets (nanopct3plus/nanopifire3/nanopim3.png) already in armbian.github.io. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: add HDMI/display bring-up driver (phase 1) + enable it Kernel patch 0023 adds a minimal drivers/gpu/drm/nexell platform driver that ungates the two DISPLAYTOP clkgen modules feeding HDMI and reports hotplug (HPD). HW-verified on a NanoPi Fire3 with a monitor attached: the HDMI block goes from clock-gated (all-zero) to live and HPD reads "monitor CONNECTED". DT: 'nexell,s5p6818-display' node in s5p6818.dtsi, enabled in the shared s5p6818-nanopi3-common.dtsi (every board in the family has HDMI). Config: CONFIG_DRM_NEXELL=y in linux-s5p6818-current.config. This is the foundation for the display pipeline; the DPC video timing, HDMI PHY preset + Link/Core, MLC plane and the atomic-KMS glue come next. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: HDMI output - test pattern via MLC (phase 2) Kernel patch 0024: the display driver now puts a stable picture on the HDMI monitor. It piggy-backs on the 1280x720 pipeline the FriendlyARM u-boot already runs for its boot logo - allocating a CMA framebuffer, painting colour bars, and pointing MLC.0 RGB layer 0 at it (disabling the u-boot layer that was scanning out reused kernel RAM as noise). Adds the DRM-free vendor MLC register layer (soc/s5pxx18_soc_mlc.c). HW-verified on a NanoPi Fire3: eight stable colour bars over HDMI - the first HDMI output from the S5P6818 on a mainline kernel. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: framebuffer console on HDMI (phase 3) Kernel patch 0025: register the MLC framebuffer as /dev/fb0 so the framebuffer console binds - the kernel log and a getty login now appear on the HDMI monitor (1280x720). Adds the required FB_CFB_*/FRAMEBUFFER_CONSOLE/FONT_8x16/VT symbols to linux-s5p6818-current.config. HW-verified on a NanoPi Fire3: fbcon at 160x45, /dev/fb0 present, login prompt on screen. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: atomic KMS display driver - /dev/dri/card0 on HDMI (phase 4) Kernel patch 0026: the display driver is now a real atomic-KMS driver (drm_simple_display_pipe + drm_gem_dma) exposing /dev/dri/card0 and a DRM fbdev console on HDMI - so the board can run Wayland/X/a desktop. It reuses the 1280x720 pipeline the bootloader sets up (the pipe drives MLC.0 from the DRM framebuffer). DRM_NEXELL becomes tristate; the DRM stack is built in (CONFIG_DRM=y + KMS/GEM-DMA/CLIENT helpers) so the console is available early. HW-verified on a NanoPi Fire3: /dev/dri/card0, [drm] Initialized nexell, framebuffer console on the monitor. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: read HDMI EDID over the DDC (i2c_1) Kernel patch 0027: the display driver now reads the monitor EDID over the HDMI DDC (i2c_1) and reports its real modes + physical size. A ddc-i2c-bus phandle is added to the display DT node. Usable mode stays 1280x720 (via mode_valid) until the DPC/PHY are self-programmed. HW-verified on a NanoPi Fire3 (monitor 600x340mm, EDID 720p timings). Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: self-program DPC timing + HDMI PHY (own modeset) Kernel patch 0028: the display driver now programmes the DPC video timing and HDMI PHY/Link preset itself for the requested mode, independent of the bootloader's boot-logo pipeline, and supports the preset-backed modes (480p/576p/720p/1080p ...) intersected with the monitor EDID. Integrates the vendor SoC layer (dp_dev/soc_dpc/dp_hdmi/hdmi_presets/soc_disptop/reg_hdmi), decoupled from the old KMS glue via a small SoC-only header. HW-verified on a NanoPi Fire3: HDMI PHY reprogrammed + locked, console renders from the self-programmed pipeline. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: Mali-400 GPU 3D acceleration via Lima Kernel patch 0029 adds the Mali-400 MP4 GPU DT node (gpu@c0070000) + the VR clock for the Lima driver; config enables CONFIG_DRM_LIMA=y (+ PM_DEVFREQ). HW-verified on a NanoPi Fire3: lima probes GP + 4 PPs, /dev/dri/renderD128 appears - GLES2 hardware acceleration on mainline, PRIME-shared to the nexell KMS display. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: HDMI audio (S/PDIF transmitter -> HDMI) Kernel patch 0030 adds the Nexell S/PDIF-TX ASoC CPU DAI + a sound-hdmi simple-audio-card (spdiftx -> spdif-dit) so audio plays over HDMI (the SPDIF-TX is internally wired to the HDMI controller). Config enables SND_SOC_NEXELL_SPDIF + SND_SOC_SPDIF. HW-verified on a NanoPi Fire3: 'S5P6818-HDMI' ALSA card, 440 Hz tone audible on the monitor speakers. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: address code review (CodeRabbit) - real bugs in the patch series Fix the legitimate issues flagged on PR #10674, verified by a from-framework build (all 30 patches apply + compile, image builds): - clk (0004): clk_dev_set_rate() now returns 0 on success (clk core treats a non-zero return as failure), and avoids truncating the rate to int. - rtc (0009): validate the 2nd MEM resource (NULL -> -ENODEV) and check ioremap() for NULL (it returns NULL, not ERR_PTR); drop the bogus free_irq() in remove (the IRQ is devm-managed). - thermal (0011): report a TIEOFF ioremap failure and fail probe instead of silently leaving the sensor unstarted (which would report bogus temps). - i2s (0016): move sleeping clk_prepare_enable()/disable_unprepare() out of the spinlock (start/stop/remove) to avoid "sleeping in atomic"; use on-stack IRQ flags instead of a shared struct field (SMP race); cast to long in the 256/384fs distance compare; make of_property_read_u32() targets u32. - edid (0027): always offer the fixed 720p mode and fini the KMS poll on teardown. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: address second CodeRabbit review round - rtc (0009): RTC_TIME_MAX was 2025.12.31, so any date past it (now!) treated a good clock as corrupt and reset to 2009 - use the full hardware counter range instead. IRQ handler now reads RTC_INT_PND (pending) not the enable register. - i2s (0016): cutoff_master_clock() must run before status is cleared, otherwise it bails on the cleared POWER bit and leaks the MCLK enable on unbind (regression from the first-round fix). - drm nexell (0027): drm_kms_helper_poll_fini() before drm_atomic_helper_shutdown() so the poll worker can't run mid-teardown. - spdif-tx (0030): add hw_free to balance the clk_prepare_enable done in hw_params. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: set KERNEL_TEST_TARGET and INTRODUCED on the three boards Declare KERNEL_TEST_TARGET="current" (the only kernel target these boards have) so autotests pick them up, and set INTRODUCED to each board's hardware release year: NanoPi M3 / NanoPC-T3 in 2016, NanoPC-T3+ and NanoPi Fire3 in 2017. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: limit to one A53 cluster (nr_cpus=4) for stability The octa-core S5P6818 is two Cortex-A53 quad-clusters behind a CCI-400. The prebuilt 2016 fork u-boot brings cluster1 online via PSCI CPU_ON but never enables the interconnect snoop/DVM for it, so cluster1 runs non-coherent with cluster0. Under multi-core load this silently corrupts memory - segfaults, malloc/tcache aborts, stack-smashing, SIGILL - which made the GNOME desktop image unusable (aborts at first-login / session start). Bisected on a NanoPi M3: the corruption is load-dependent but frequency-independent (fails identically at 800 and 400 MHz), not thermal (crashes at 42C with a heatsink), not power (two supplies, same rate) and not DRAM (0 errors, sequential and random). CPUECTLR.SMPEN is set on all cores. The discriminator: 8 cores (both clusters) = ~10% failures under stress; 4 cores (cluster0 only) = 0 failures. So it is cross-cluster cache coherency. Restrict Linux to cluster0 until the boot blob's PSCI is fixed to enable CCI coherency for cluster1 (which will recover all 8 cores). Applies to all three S5P6818 boards (nanopct3plus, nanopim3, nanopifire3) via the shared boot script. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: move from current to edge kernel branch Per review (EvilOlaf): 7.2 is a non-LTS kernel ahead of the latest LTS, so the S5P6818 revival belongs on the edge branch, not current. There is no LTS/current target for this SoC yet. Rename KERNEL_TARGET/KERNEL_TEST_TARGET to edge on all three boards (nanopct3plus, nanopim3, nanopifire3), rename the kernel config (linux-s5p6818-current.config -> linux-s5p6818-edge.config) and switch the family branch case to edge. The KERNELPATCHDIR (archive/s5p6818-7.2) is version-based and unchanged. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: address third CodeRabbit review round (minor/major fixes) - i2c (0008): return probe failure if reset_control_reset() fails, before enabling the controller. - thermal (0011): drop the unused S5P6818_TMU_REG_EMUL_CON define and the "emulation" claim from the commit message (emulation stays on the exynos4412 callback; the 0x100 define was dead). - dts pinctrl (0012): rename pinctrl@c0010000 -> pinctrl@c001a000 to match the first reg entry (dtc unit_address_vs_reg). - power-reset (0013): add a .remove that unregisters the restart handler and iounmaps the window, so unbind can't leave a dangling notifier/mapping. - i2s (0016): constrain the advertised DAI rate to the DT sample-rate (the master clock is programmed once and hw_params does not reprogram it), so an open at another rate can't play at the wrong pitch. - dts eMMC (0018): comment said 8-bit; the node is bus-width = <4>. Fix to 4-bit. - kernel config: SND_SOC_NEXELL_SPDIF / SND_SOC_SPDIF were =y under =m parents (SND_SOC=m); set them =m to match, consistent with SND_SOC_NEXELL_I2S. - boot script: honour console= from armbianEnv.txt (serial/display/both, default both) instead of hardcoding both consoles and ignoring ${console}. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: drop FULL_DESKTOP from the three boards The desktop is not usable yet: GNOME (and any Wayland compositor) hard-hangs the board in the nexell DRM atomic-commit/page-flip path, independent of the GL backend (reproduces with software rendering too). Until that driver hang is fixed the S5P6818 boards are CLI/server-grade, so stop advertising a full desktop. Restore once the KMS driver is stable under a compositor. Signed-off-by: Igor Pecovnik <igor@armbian.com> * s5p6818: pin Lima runtime PM to fix GPU resume hard-wedge The Mali-400 works from the bootloader power-up, but the first runtime-PM suspend/resume cycle hard-wedges the whole SoC: the reset-deassert + GPU re-init on resume hangs the interconnect (LED heartbeat stops). Reproducible with `echo on > .../c0070000.gpu/power/control`, and the cause of every compositor hang (mutter idles->suspends->resumes the GPU each frame). The clock is not the cause (VR clock reads enabled across the wedge) - the boot blob's GPU clock/reset handoff is not re-entrant. Pin a runtime-PM reference in lima probe on this SoC (guarded by the nexell,s5p6818 machine compatible) so the GPU stays in its known-good boot state and never suspend/resume-cycles. Clock stays on, GLES2 keeps working; only GPU runtime power-gating is given up. Signed-off-by: Igor Pecovnik <igor@armbian.com> --------- Signed-off-by: Igor Pecovnik <igor@armbian.com> | 7 天前 | |
bootscript: document EEPROM layout and board codes in detail | 4 天前 | |
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 | 1 个月前 | |
SpacemiT K3: Pico ITX: Transition from extlinux to boot scr Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 14 天前 | |
bootscript: Remove vendor name and slash from DTB file name After that, the script successfully loads the DTB file from two possible paths and overlays. If the file does not exist, then the default file will be uploaded. | 1 年前 | |
`orangepizero2`/`sun50iw9`/`legacy`: implement `pre_package_kernel_image` hook to convert vmlinuz to uImage manually; fix legacy u-boot build - sourceaddr `0x40008000` was found in Xunlong's legacy kernel source squashed into a huge commit. Thanks, Xunlong! - bring `busybox` dependency with inline hook for legacy u-boot "unix2dos" which is essential | 3 年前 | |
orangepi4pro: Add community support for Orange Pi 4 Pro (Allwinner A733) [new files only] (#9967) | 2 个月前 | |
bootscript: sunxi: Delete the vendor's name from the fdtfile variable Do not inform the user if the fixup.scr file was not found. | 1 年前 | |
udoo: boot script use ${fdtfile} (modern findfdt), not ${fdt_file} After the device-number fix, zImage/uInitrd load fine but the dtb load failed with "Failed to load '/boot/dtb/'" -> bootz aborts ("Did not find a cmdline Flattened Device Tree"). Modern u-boot's findfdt sets ${fdtfile} (imx6q-udoo.dtb / imx6dl-udoo.dtb by SoC), but the old script read ${fdt_file}, which is unset on v2026.07. Use ${fdtfile}; fall back to ${fdt_file} then imx6q-udoo.dtb if unset. Matches the modern imx6 pattern already used by boot-cubox.cmd, loading the dtb flat from /boot/dtb/ as Armbian lays it out. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 2 个月前 | |
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) | 1 年前 | |
Add Avnet MicroZed | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 2 个月前 | ||
| 4 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 2 个月前 | ||
| 4 个月前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 4 年前 | ||
| 7 年前 | ||
| 2 年前 | ||
| 23 天前 | ||
| 23 天前 | ||
| 2 年前 | ||
| 7 年前 | ||
| 9 个月前 | ||
| 8 个月前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 10 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 2 年前 | ||
| 4 个月前 | ||
| 2 个月前 | ||
| 7 天前 | ||
| 4 天前 | ||
| 1 个月前 | ||
| 14 天前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 2 个月前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 1 年前 | ||
| 5 年前 |