RSS Bot

Description Maint. How Has This Been Tested? [ ] CI Checklist: [ ] My changes generate no new warnings View the full article

Description This PR moves OPi5 series Uboots to Radxa tree and gets rid of Xunlong uboot completely. How Has This Been Tested? [x] Opi 5 boots w/o SPI flash with newer Uboot [x] Opi 5 Plus boots w/o SPI flash with newer Uboot [x] Opi 5 Plus boots with NVME SSD Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This reverts commit 11245601d095645d2973a0e765ee0f9a01d51cc1. Fix doesn't work correctly. How Has This Been Tested? [ ] CI Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As discussed in https://github.com/armbian/build/issues/6835 Deprecate legacy, but only remove from board configs for now. Print a warning, the whole branch is slated for removal. @efectn Please have a look at Opi5, there was some functions in the board config uboot_add_sata_target @amazingfate @igorpecovnik I think it would be best to change the default branch in the vendor kernel repo to the new 6.1-rk3 https://github.com/armbian/linux-rockchip what do you think? GitHub issue reference: https://github.com/armbian/build/issues/6835 Jira reference number AR-2394 How Has This Been Tested? [x] ./compile.sh kernel BOARD=nanopi-r6s BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie -> New deprecation warning appears Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The legacy U-Boot can't be built anymore and 4.4 is EOL. As discussed in https://github.com/armbian/build/issues/6821#issuecomment-2205234200 I didn't see any kernel or uboot patch folder. If I forgot something related to legacy, please let me know :) GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas View the full article

add board bigtreetech-cb2: BigTreeTech CB2 add board bigtreetech-cb2: BigTreeTech CB2 Co-authored-by: Ricardo Pardini ricardo@pardini.net View the full article

u-boot: use pipetty in place of unbuffer u-boot: use pipetty in place of unbuffer unbuffer never solved anything; pipetty might View the full article

mixtile-blade3: use default blobs & bump vendor u-boot to next-dev-v2024.03 mixtile-blade3: rk3588: u-boot: rewrite u-boot patches, no changes rewritten against ddc91cd08c10f625f7a7c93033042aa4071c78a8 - a specific commit in radxa's next-dev mixtile-blade3: rk3588: u-boot: bump to next-dev-v2024.03 drop 0004-cmd-source-fix-the-error-that-the-command-source-failed-to-execute.patch rebase the others mixtile-blade3: use default blobs View the full article

mekotronics: rk3588: u-boot: borrow patch to fix build on newer gcc mekotronics: rk3588: u-boot: rewrite u-boot patches, no changes rewritten against 609a77ef6e99c56aacd4b8d8f9c3056378f9c761 - a specific commit in radxa's next-dev mekotronics: rk3588: u-boot: borrow patch to fix build on newer gcc View the full article

git: git_ensure_safe_directory(): use env vars instead of changing config git: git_ensure_safe_directory(): use env vars instead of changing config View the full article

Description The family consists of 4 boards, but hasn't seen any activity in years, is unmaintained, stuck on EOL Linux 4.14 and the bootloader does not build. Thus remove the kernel, the family and the boards which have been unmaintained for some years unfortunately. See https://github.com/armbian/build/issues/6821#issuecomment-2200664955 If you have any objections for this removal or would like to maintain these boards, please tell :) If at some point in the future someone wants to bring back one of those boards, they can find this PR/commit through a GitHub search. But there wasn't too much information removed, to support new kernels >=6.6, work would likely have to be started from scratch anyways. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 Checklist: [x] I have performed a self-review of my own code View the full article

Description Fix build errors on Khadas Edge 2 vendor uboot. GitHub issue reference: https://github.com/armbian/build/issues/6862 Jira reference number AR-2402 How Has This Been Tested? [x] Now it builds with DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:noble" argument. Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Some older U-Boot versions don't use semantic versioning in their code and will fail when building libfdt. This is fixed by hardcoding a semantic version. rk35xx used a very old branch from Radxa vendor U-Boot and won't build with GCC13. Bump it to the latest version. GitHub issue reference: https://github.com/armbian/build/issues/6862 Jira reference number AR-2402 How Has This Been Tested? [x] ./compile.sh uboot BOARD=radxa-e25 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble ARTIFACT_IGNORE_CACHE=yes [x] ./compile.sh uboot BOARD=nanopi-r2s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble ARTIFACT_IGNORE_CACHE=yes [x] ./compile.sh uboot BOARD=nanopineo3 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble ARTIFACT_IGNORE_CACHE=yes @efectn Building OrangePi5 U-Boot from Xunlong also fails on Ubuntu 24.04. Please consider using the default Radxa U-Boot for rk3588 by removing the extra lines from the OrangePi5 configs. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The Recore dts patch submitted earlier was not applied since the patch was not not referenced in the series.conf file. The patch adds it to the list. Documentation summary for feature / change [x] short description (copy / paste of PR title) [x] summary (description relevant for end users) [ ] example of usage (how to see this in function) How Has This Been Tested? It has been tested on the following hardware: [x] Recore A8 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description sunxi64-current had been frozen since release. Bump it to most recent tag at this date. Documentation summary for feature / change Removed a patch from Megi's which per description saves 20ms per something on boot which caused kernel compile breakage between 6.6.34 and .35. How Has This Been Tested? [x] Build kernel for Orange Pi Zero 2 with current: https://paste.armbian.de/domaniqife [ ] Boot tests on various sunxi64 boards should be done before merge! Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Added patches and config for BigTreeTech CB2/Pi2 GitHub issue reference: Jira reference number AR-2332 How Has This Been Tested? Build and load on BTT Pi 2, test peripherals [ ] UART on the type-c port [ ] Ethernet [ ] WiFi [ ] NVMe [ ] HDMI [ ] other peripherals Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Update support for Recore boards Adding support for Recore 3D printer control boards A5 through A8. There is support for these boards in an older version of build, but they don't seem to have been propagated. There are some improvements in this version (thus the "update" in the description) and also support for a newer version of the hardware. Recore is a 3D printer control board. Documentation summary for feature / change [x] short description (copy / paste of PR title) [x] summary (description relevant for end users) How Has This Been Tested? It has been tested on the following hardware: [x] Recore A5 [x] Recore A6 [x] Recore A7 [x] Recore A8 Checklist: [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description Fix #6857 and add 10 seconds network timeout to initramfs ssh daemon waiting for cryptroot-unlock password GitHub issue reference: #6857 Jira reference number [AR-2401] How Has This Been Tested? [x] Succesfully running CRYPTROOT_ENABLE="y" nanopi-r5c [x] Succesfully running CRYPTROOT_ENABLE="y" orangepi5-plus Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Bumps setuptools from 70.1.1 to 70.2.0. Changelog Sourced from setuptools's changelog. v70.2.0 Features Updated distutils including significant changes to support Cygwin and mingw compilers. (#4444) Bugfixes Fix distribution name normalisation (:pep:625) for valid versions that are not canonical (e.g. 1.0-2). (#4434) Commits 3accd5c Bump version: 70.1.1 → 70.2.0 719192a Merge pull request #4430 from pypa/infra/refresh-skeleton e32f8df Merge pull request #4444 from pypa/feature/distutils-f3b225449 343ac6f Merge https://github.com/pypa/distutils into feature/distutils-f3b225449 4e6d97d Prefer relative imports for better portability. 449021c Merge pull request #4442 from DimitriPapadopoulos/default 97e3c8f Merge pull request #4452 from pypa/docs/1648-interpolation a9a5400 Add a section on interpolation. 31c8599 Remove 'normally supplied to setup()'. Declarative styles are normalized. ad8c7ba Merge pull request #4450 from DimitriPapadopoulos/TRY Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Description Move tv-box based rk3318-box and rk322x-box target to use u-boot v2024.07-rc5 from v2024.01, mostly for experimentation and also because v2024.07 contains some fixes for rockchip devices explained in this previous PR: https://github.com/armbian/build/pull/6731, in particular we can leverage uboot relocation for rockchip 64 bit devices and rk3328 hdmi/vop/phy drivers are now mainlined. This PR also rework hdmi/vop/phy patches for rk322x and fixes usb issues on rk3318-box The changes does not affect any other board, since none of them actually use v2024.07 of uboot (at the moment of writing the comment, it is still in RC5). The v2024.07 patch directory has been prepared though and it is ready for others to jump in. GitHub issue reference: Jira reference number AR-2400 How Has This Been Tested? [x] Various tests on rk322x-box system, including boot from sdcard, boot from emmc and checks about the expected boot order (sdcard -> usb -> emmc) [x] Same as above on rk3318-box system Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Description We really, really don't need to keep legacy factory Allwinner wonder SDK 4.9.y in our framework. Jira reference number AR-2399 How Has This Been Tested? [x] CI Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Rockchip has released new sdk with rk3576 support and kernel's tag is linux-6.1-stan-rkr3. I have rebased commits from rkr1 to rkr3 and this pr depends on https://github.com/armbian/linux-rockchip/pull/200. Prebuilt kernel can get downloaded from github actions: https://github.com/armbian/linux-rockchip/actions/runs/9740746614?pr=200 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=rock-5b BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow [x] Kernel boots fine on rock5b. [ ] rk356x boards need test [ ] rk3528 boads need test [ ] Other rk3588 boards need test Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Helping @SeeleVolleri from: https://github.com/armbian/build/pull/6849 The default 2017.09 u-boot for rk3588 doesn't seem to work on this board with the generic config. Try mainline u-boot. Reference: https://github.com/armbian/build/pull/6834#issuecomment-2198765229 @SeeleVolleri Please test if this works :) You can edit this message to add your tests as well. How Has This Been Tested? [ ] Test A Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings View the full article

Description Please note that this PR does not merge to main, but to another branch for collaboration. This is a continuation of v2: https://github.com/armbian/build/pull/6800 @pyavitz has already done a nice job in v1 and v2 of this PR. Based on this work, I have put a lot of effort in trying to bring this new board family more in line with existing families as well as trying to improve maintainability for the long term. Another concern with v2 was the sheer size of the PR (~55MB which amounts to almost 10% of the repo or ~2.4 million LOC which amounts to over 50% of the current repo). v3 brings down this size considerably, to a more sane number: v2 v3 Shrinkage Lines of code 2 402 910 495 249 ~80% PR size ~ 55 MB ~17.5 MB ~66% This is possible due to using external repos for e.g. WiFi driver and vendor kernel instead of completely patching it in. Other than that, changes from v2 to v3: Include all improvements from @pyavitz into the original files/commits Use boot source directly from vendor -> only few patches needed Use vendor kernel source for legacy --> only few patches needed Use our own repo for RTL8852BS WiFi driver --> no patch needed (was huge before) Revise commit messages Downgrade BananaPi F3 to CSC since @pyavitz does not plan to be a maintainer Other little fixes and improvements like using our dt auto-patcher to make it easy to develop and add new boards Please see the commit messages for more details. To-Do I left all functionality as before, so both legacy and current kernels are still there along with the other stuff. We still need to think about whether it makes sense to keep both unless a maintainer wants to step up. But with the v3 changes, legacy and U-Boot will be a breeze to maintain. [ ] Rewrite kernel patches after they're "done" and not changing much anymore (feel free to add more tasks) How Has This Been Tested? [x] ./compile.sh kernel BOARD=bananapif3 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh kernel BOARD=bananapif3 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh uboot BOARD=bananapif3 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh build BOARD=bananapif3 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [ ] Test flashing image with legacy kernel [ ] Test flashing image with current kernel Information on BananaPi F3 (Following info by @pyavitz from v2) Bluetooth firmware added to armbian/firmware. esos.elf added to: packages/blobs/riscv64/spacemit/ https://docs.banana-pi.org/en/BPI-F3/BananaPi_BPI-F3 https://gitee.com/bianbu-linux Flashing u-boot to eMMC: (This is not apart of the PR and needs to be added in the future.) echo 0 > /sys/block/mmcblk2boot0/force_ro sleep .50 dd if="bootinfo_emmc.bin" of="/dev/mmcblk2boot0" bs=512 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=1 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=512 conv=notrunc dd if="fw_dynamic.itb" of="/dev/mmcblk2" bs=512 seek=1280 conv=notrunc dd if="u-boot.itb" of="/dev/mmcblk2" bs=512 seek=2048 conv=notrunc sync Tested: Bluetooth and Wifi (useless without an ANT) (bluetooth is iffy) Ethernet (1 and 2) PCIe USB HDMI (LEGACY) Debug UART NOTE: One major difference between this build and the others available else where is the use of SYSLINUX/EXTLINUX instead of the ENV file. BUGS: HDMI currently broke on CURRENT. The screen just displays red. [ 5.132172] [drm:dpu_init] *ERROR* dpu_init wait cfg ready done timeout [ 5.132883] [drm:dpu_isr] *ERROR* Under Run! DPU_Mclk = 0, DPU BW = 0 View the full article

Description Change to mainline uboot, fixed not booting issue, added hdmi0 audio interface alias. How Has This Been Tested? [x] ./compile.sh build BOARD=firefly-itx-3588j BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers internet' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm [x] Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article