RSS Bot

Description A new issue template for Tasks will make project/task tracking easier on GitHub. See for example how Pi-Hole does project tracking: https://github.com/orgs/pi-hole/projects/22 The tasks will be automatically uploaded to Jira, so no changes there. How Has This Been Tested? [ ] To be tested in future issues 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 View the full article

Description station-m2: update u-boot patches. Add u-boot device tree for station-m2. How Has This Been Tested? [x] Successfully built. [x] System startup. 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

With each board running a mainline-first Linux software stack and tested in a CI loop with the LAVA test framework, the Farm showcased Collabora's recent hardware enablement and Continuous integration (CI) efforts. View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: [] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) 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. [ ] Test A [ ] Test B 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

rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions in practice: boards that didn't specify their own blobs: bump DDR 1.08->1.16 ; BL31 1.28 -> 1.45 (example: rock-5b!) boards that specified 1.16/1.45 individually now follow the defaults (no change) boards that specified a different version: no change; just a TODO suggesting review/removal/go-with-the-defaults Mekotronics boards: bump from 1.11/1.38 to defaults (1.16 / 1.45) View the full article

fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host otherwise:fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1 has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer version of e2fsck! orphan_file can only be disabled on recent-enough e2fsprogs, thus check version and compare View the full article

kde-neon: use Neon's "user" repo for Jammy & return it to csc status kde-neon: use Neon's "user" repo for Jammy & return it to csc status for noble: keep on Neon's "testing" repo which now has a "noble" dist (instead of Jammy) - but keep it eos as it really doesn't build yet. See https://blog.neon.kde.org/2024/05/09/kde-neon-rebasing-on-ubuntu-noble/ - might take a while still View the full article

Description The color hex code cannot be prefixed with #. See https://github.com/armbian/build/actions/runs/9683062190/job/26717603287 How Has This Been Tested? [ ] To be tested in future PRs Checklist: [x] My code follows the style guidelines of this project View the full article

WirePlumber 0.5 arrived recently with many new and essential features including the Smart Filter Policy, enabling audio filters to automatically insert themselves in between client streams and devices. View the full article

Description This example PR: https://github.com/armbian/build/pull/6804 has the "Framework" label while it only changes stuff in a bsp package. To make it clearer, add a new label for the auto-labeler. How Has This Been Tested? [ ] To be tested in future PRs 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 [ ] My changes generate no new warnings View the full article

Description We can also use rkvdec2 on rk356x. Remove all non-coherent-dst-bufs patches because they are suggested by a chromium developer when using libyuvimageprocessor to do NV12->AR24 convert. Now we use wayland gbm to render NV12 directly, so these patches are not necessary. Add rkvdec2 nodes to devicetree of rk356x. Enable rkvdec2 in kernel config and change CMA size from 128M to 384M for chromium's 4K h264 decoding. Change hantro g1 vpu compatible string from rockchip,rk3568-vpu to rockchip,rk3328-vpu because they have exactly the same vpu variant data. Disable h264 decoder of rk3328-vpu because there are aleady rkvdec/rkvdec2 h264 decoders on rk3328 and rk356x. Multi H264 decoders will make gstreamer and chromium confused. Add chromium v4l2 decoder udev rule for rk3328-vpu 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] Tested on orangepi3b noble edge with chromium from my ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/chromium, 1080p and 2160p h264 videos and 1080p vp8 video are played with hardware decoder. 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

Changes to be committed: modified: config/boards/aml-s9xx-box.tvb modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template The aml-s9xx-box builds use the native TV Box u-boot. I've had as a todo item to figure out how to not build and include an unused u-boot. In a recent PR for a different board the opposite was being done (adding a u-boot where a board didn't previously ship one), thus I then had the info to remove it here. This also changes the generated extlinux.conf to include a fdt line by adding the boot_fdt_file to the board config file. This reduces the effort needed to manually modify the extlinux.conf. How Has This Been Tested? [x] Build aml-s9xx-box image and debs [x] Verify built contents 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 View the full article

Description This PR is a cherry-picked commit from an old PR https://github.com/armbian/build/pull/4643 Unfortunately I seem to have borked the linked PR. Using git rebase main usually works, but with a PR going this far back, something seems to not have rebased as expected. Please let me know if you know why this is 😄 The commit includes a fix from https://github.com/armbian/build/commit/7488222b2aac8bc6a395b6714dbac3f88177585e View the full article

This picks up from where we left off: https://github.com/armbian/build/pull/6771 Added Linux Legacy and Current. Legacy: 6.1.15 Current: 6.1.95 Wireless has been given its own function and patch directory. Bluetooth firmware added to armbian/firmware. esos.elf moved to: packages/blobs/riscv64/spacemit/ Host machine used for builds: Ubuntu Noble (aarch64) Images tested: Ubuntu Noble Minimal and Debian Sid Information: 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) Ethernet (1 and 2) PCIe USB HDMI 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. View the full article

Description disable add requirements.txt to Dockerfile generation How Has This Been Tested? [x] Manual build passes Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Changes to be committed: modified: aml-s9xx-box.tvb PR #6659 broke upgrades for the aml-s9xx-box package. That PR introduced two new files in /boot which is a fat filesystem on this box. The standard package upgrade fails on a fat filesystem when files already exist. PR #6659 failed to add the files to the remove list. This PR does that. 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] build aml-s9xx-box image and debs [x] test upgrade of the bsp-cli deb Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description If we want to check if a file is not from one of the listed folders, it needs to be check that "NOT x AND NOT y AND NOT z" is true, instead of "NOT x OR NOT y OR NOT z" Example: This PR should not have the "Hardware" label: https://github.com/armbian/build/pull/6781 How Has This Been Tested? [ ] To be tested in future PRs Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description Update and run our shellfmt script version 3.8.0 How Has This Been Tested? [x] Run sudo ./lib/tools/shellfmt.sh 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 Bump the 6.10 kernel from 6.10-rc4 to 6.10-rc5. Includes kernel config rewrite for RK3588. How Has This Been Tested? [x] Build success: ./compile.sh BOARD=nanopi-r6c BRANCH=edge RELEASE=trixie EXPERT=yes KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no EXTRAWIFI=no kernel 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Jira reference number AR-2385 How Has This Been Tested? [x] Tested on forums, officially released images will be tested before relese Checklist: [x] My code follows the style guidelines of this project View the full article

Description phytium-embedded: add bpf_syscall support. update kernel config. How Has This Been Tested? [x] Successfully built. [x] System startup. 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 Add uarts dts as per vendor spec 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] Built orangepi5-plus with kernel 6.8 and connected serial gps to uart3-m1 ttyS3 - got a fix 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

networking: main-config: introduce NETWORKING_STACK to control network exts; allow "none"; fix typo networking: exts: introduce sanity checks, debug info protect against enabling networking exts directly debug logging fix typo in ext name networking: main-config: introduce NETWORKING_STACK to control network exts; allow "none"; fix typo NETWORKING_STACK can be set to none (in config phase, pre-extensions) to not-add any networking extensions keep defaulting to systemd-networkd if BUILD_MINIMAL and NetworkManager otherwise fix typo in extension name add NETWORKING_STACK to change-tracking View the full article

Description Closing https://github.com/armbian/build/issues/6773 Jira reference number AR-2382 How Has This Been Tested? [x] When netplan random mac defs are present, device (Odroid M1) does not get IP Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Starting from Linux kernel v5.4, the HAVEGED inspired algorithm has been included in the Linux kernel, see the LKML article and the Linux Kernel commit. Additionally, since v5.6, as soon as the CRNG (the Linux cryptographic-strength random number generator) gets ready, /dev/random does not block on reads anymore: see this commit. SOURCE: jirka-h/haveged How Has This Been Tested? [x] Succesfully built nanopi-r5c BRANCH="current" RELEASE="jammy, bookworm, noble, trixie" 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