RSS Bot

Description The latest migration to 6.10 broke some functions of Khadas Edge2 board. This PR fixes them. Jira reference number [AR-9999] How Has This Been Tested? [x] Auto fan control works. [x] Typec works again. 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 Update JetHome JetHub D2 support: add patchset for u-boot update kernel patches Update #6725 Jira reference number AR-2028 View the full article

rockchip-rk3588 6.8.y: nanopct6: Add NanoPC T6 SPI Flash (v6.8.y version) rockchip-rk3588 6.8.y: nanopct6: Add NanoPC T6 SPI Flash (v6.8.y version) View the full article

Description Add a patch series to support VEPU121/VPU121, which mainly enables hardware decoding for H.264. It can also decode MPEG2 and VP8 as well as do JPEG encoding. Usually I am against bloating the kernel with patches since it makes it more difficult to maintain. But having access to the RK3588's H.264 decoder is really useful for day to day tasks. How Has This Been Tested? [ ] Needs some testing View the full article

Part 3 of the cmtp-responder series with a focus on USB gadgets explores several new elements including a unified build environment with Docker and an example strategy for building and deploying to a target. View the full article

Description Move stack pointer further from base address to allow bigger uboot images. Currently uboot stack pointer located 1MiB after text base, and uboot size with defconfig is barely less than 1MiB (1001472). So any small modification in code/config/compiler-version could overflow text area (my uboot blown up after I enabled verbose logging to debug btrfs boot problem). How Has This Been Tested? [x] Build and boot rk3318-box Checklist: [x] I have performed a self-review of my own code View the full article

Add audio support to hdmi output (meson) View the full article

Description Find and take loop device in one shot to prevent race condition How Has This Been Tested? [x] Build image Checklist: [x] I have performed a self-review of my own code View the full article

Description Bump sm8250 current to 6.9 based on postmarketos's branch: https://gitlab.com/sm8250-mainline/linux/-/tree/sm8250/v6.9?ref_type=heads. Panel and touch screen patches from 6.7 are dropped because they are never enabled in kernel config. In 6.9 bluetooth of qca6390 won't work with default address hardcoded in driver, and setting a new address of bluetooth can make it work again, so I add a service to generate bluetooth address based on /etc/machine-id, 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 kernel BOARD=xiaomi-elish BRANCH=current DEB_COMPRESS=xz [x] Tested with xiaomi-elish, panel, gpu, vpu, sound works. Note: noble gnome's pipewire will make speaker sound very low, pulseaudio can make it work sometimes. 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description FriendlyElec ships their devices with the latest blobs. Trying to run an Armbian image on this board with the old blobs might cause issues. @rpardini run into those issues with the NanoPC T6 and fixed it in https://github.com/armbian/build/pull/6711 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 JetHome Jethub D2 (j200) is a home automation controller with the following features: DIN Rail Mounting Amlogic S905X3 (ARM Cortex-A55) quad-core micro-HDMI video out 4GB LPDDR4 32GB eMMC flash 1 x USB 2.0 1 x 10/100/1000Mbps ethernet two module slots for radio/wire interface cards 2 x gpio LEDS 1 x 1-Wire 1 x RS-485 3 x dry contact digital GPIO inputs 2 x relay GPIO outputs DC 9-36V power source with battery UPS on board option Jira reference number AR-2028 How Has This Been Tested? Build and run ok. [X] JetHub D2 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 View the full article

Description sun55iw3-syterkit: 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 Helping @alexl83 with his OrangePi 5 Plus 😄 Support for this board with SPI image was added to U-Boot this january: https://github.com/u-boot/u-boot/commit/7c084fd51c0c52b24facdbcfeeaf2c70fba03406 Also add the latest DDR and BL31 blobs, this should fix issues like recently on the NanoPC T6. Marked as WIP to give room for testing. How Has This Been Tested? [x] Build success: ./compile.sh BOARD=orangepi5-plus BRANCH=edge RELEASE=trixie EXPERT=yes KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no uboot [ ] @alexl83 please test freshly built edge kernel image [ ] @alexl83 please test freshly built vendor kernel image (vendor u-boot should be applied) [ ] @alexl83 please test edge image on SD card while vendor U-Boot is installed in SPI (or wherever it lives when it comes from the factory) 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

the unthinkable: rockchip-rk3588 current (to 6.8.12, EOL and non-LTS!) and edge to 6.10-rc2 (from #6699) first move stuff around first I called the old 6.8.y oldedge, later renamed to current (!) .config's for edge and current are now version-filenamed rk3588: edge: Bump kernel from 6.8 to 6.10 Bump mainline kernel from 6.10-rc1 to 6.10-rc2 Remove patches which are now mainlined Re-number "fix-initial-PERST-GPIO-value" patch as per number ordering seen in 0000.patching_config.yaml Rewrite kernel config rk3588: edge: Fix dtb overlay compilation and installation "general-add-overlay-compilation-support.patch" became obsolete in Linux 6.9 (see AR-2352 [1]). Fix this problem: Rename *.dts sources in overlay directory to *.dtso Change "target +=" line to "dts-y +=" in overlay Makefile Remove "always +=" line in overlay Makefile Add .scr compilation support in kernel scripts/Makefile.lib Patch kernel scripts/Makefile.dtbinst to avoid flattening overlay directory For the last two points, see general-add-overlay-compilation-support.patch Credits for this fix go to @paolosabatino [1] https://armbian.atlassian.net/browse/AR-2352 orangepi 5: Fix patch for 6.10 and convert from patch to .dts file This simplifies the process updating to newer kernel versions and makes it easier to see and edit the actual dts file being used. khadas edge 2: Fix patch for 6.10 rk3588: edge: Update thermal and cpufreq support patches Patches are from the Linux Rockchip Mailing List, submitted by Alexey Charkov. [1] Notable improvements from changelog: Moved the TSADC enablement to per-board .dts/.dtsi files Dropped extra "inefficient" OPPs (same voltage - lower frequencies) Dropped second passive cooling trips altogether to keep things simple Added a cooling map for passive GPU cooling (in a separate patch) Added regulator coupling for EVB1 and QuartzPro64 Also enable automatic fan control on Rock 5B. [1] https://lore.kernel.org/linux-rockchip/20240506-rk-dts-additions-v4-0-271023ddfd40@gmail.com/ rk3588: edge: Rewrite kernel patches to 6.10-rc2 rk3588: edge: Patch in new HDMI controller driver The old driver didn't build on 6.10, so the kernel build couldn't finish. Link to the added patch series: https://lore.kernel.org/all/20240601-b4-rk3588-bridge-upstream-v1-0-f6203753232b@collabora.com/ rockchip-rk3588/edge: nanopct6: Add NanoPC T6 SPI Flash (6.10-rc2 version) rockchip-rk3588-edge (6.8.y) -> archive/rockchip-rk3588-6.8 (patches copied) lets move to standard patch dir for this family patches are being copied (not moved) on purpose; we've already PR open to move to 6.10-rcX rockchip-rk3588 6.8.y: nanopct6: Add NanoPC T6 SPI Flash (v6.8.y version) rockchip-rk3588: add oldedge pointing to 6.8 rockchip-rk3588/edge 6.8.y: rewrite/rebase patches against v6.8.12 (EOL) rockchip-rk3588: add oldedge pointing to 6.8; preserve .config rockchip-rk3588: add oldedge pointing to 6.8; update .config (no changes) CONFIG_EXPERT is now yes in armbian code, it reflects here rockchip-rk3588: add oldedge pointing to 6.8; convert .config to defconfig against v6.8.12 (EOL) rockchip-rk3588: move rockchip-rk3588-edge (6.10) patches to archive/rockchip-rk3588-6.10 no changes rockchip-rk3588: don't spell out KERNELPATCHDIR anymore, as we have default convention now (under archive/rockchip-rk3588-x.z) rockchip-rk3588: shellfmt, some comments on collabora (no real changes) rockchip-rk3588-6.10: rewrite patches, no changes rockchip-rk3588: current (6.8) and edge (6.10) - use major+minor in kernel config filenames LINUXCONFIG="linux-rockchip-rk3588-${KERNEL_MAJOR_MINOR}" # Attention: not -${BRANCH} (edge/current/legacy), -but ${KERNEL_MAJOR_MINOR} thus 6.8 / 6.10 etc View the full article

Description update-apt-xapian-index takes an insane amout of time during buid - compounding over dozens of builds you get a nice overhead in compute-time in the hours range This PR disables update-apt-xapian-index for unstable releases ( $BETA = yes ) 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 desktop with and without BETA=yes, results below Baseline 1st run ( CLEAN_LEVEL="debs,cache" ) Repeat Build Options [ ./compile.sh opi5plus build BRANCH=edge BUILD_DESKTOP=yes CLEAN_LEVEL=debs,cache DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools office remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=bookworm ] Runtime [ 14:54 min ] Baseline 2nd run ( CLEAN_LEVEL="debs" ) Repeat Build Options [ ./compile.sh opi5plus build BRANCH=edge BUILD_DESKTOP=yes CLEAN_LEVEL=debs DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools office remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=bookworm ] Runtime [ 5:45 min ] Baseline 3rd run ( CLEAN_LEVEL="debs" BETA="yes") Repeat Build Options [ ./compile.sh opi5plus build BETA=yes BRANCH=edge BUILD_DESKTOP=yes CLEAN_LEVEL=debs DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools office remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=bookworm ] Runtime [ 5:04 min ] Baseline 4th run ( CLEAN_LEVEL="debs,cache" BETA="yes") Repeat Build Options [ ./compile.sh opi5plus build BETA=yes BRANCH=edge BUILD_DESKTOP=yes CLEAN_LEVEL=debs,cache DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools office remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=bookworm ] Runtime [ 14:14 min ] 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

Description rk-35xx-vendor-6.1 minor touches: - move CONFIG_INPUT_RK805_PWRKEY and CONFIG_PINCTRL_RK805 to modules - move CONFIG_BT to module - add rtw89 8852be/ce wifi support via xunlong/linux-orangepi commit-id 96b2d2827a3f1e4719ebdfcac0b2108e8cbae932 see net: wireless: realtek: Sync rtw89 driver from linux6.2 linux-rockchip-rk3588-edge.config minor touches: - move CONFIG_INPUT_RK805_PWRKEY and CONFIG_PINCTRL_RK805 to modules - move CONFIG_BT to module This enables powerkey functionality for orangepi5-plus OOB Jira reference number AR-2360 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 images (and ran) vendor/edge RELEASE=trixie 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] My changes generate no new warnings View the full article

nanopct6: Kwiboo 24.07 u-boot for edge; bump blobs for all branches nanopct6: Kwiboo 24.07 u-boot for edge; bump blobs for all branches exclusive for edge / Kwiboo: enable UMS / RockUSB and other gadget stuff enable TCP networking features, wget etc enable EFI debugging stuff store environment in SPI uses preboot to flash led briefly this code pattern is becoming copypasta fast and needs refactor before it spreads too much also for all branches (legacy/vendor/edge): BOOTDELAY=1 so we can stop u-boot via UART a bit easier (also for nanopc-cm3588-nas board) can still do it with zero, but it's so much harder; and it's utility outweighs the 1-second delay IMHO nanopct6: updated blobs to DDR v1.16 and BL31 v1.45 View the full article

odroidhc4: bump to u-boot v2024.04; drop most defconfig patches in favor of hooks 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 View the full article

Description Maintenance job. We provide options to build several desktop combinations, but we don't have a mechanism for verifying if those targets still work. I developed a simple action script that cycles all variants that are either supported or community supported. Community supported will only check for deboostrap success. This commit is a result of reading build logs of that Action script. Kde-Neon is in EOS zone as it doesn't build anywhere (atm). AR-2358 How Has This Been Tested? [x] Targets were tested for (x86 qemu which will be further tested on VM once CI extents to this functionality) image compiling. 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 Due to crypto policy update, apt now (since v2.7.13, see the commit) requires repositories to be signed using one of the following public key algorithms: RSA with at least 2048-bit keys Ed25519 Ed448 Affected: Ubuntu Oracular when adding Mesa PPA. More info https://ubuntuhandbook.org/index.php/2024/04/workaround-apt-warning-signature-key-uses-weak-algorithm/ Jira reference number AR-2359 How Has This Been Tested? [x] https://github.com/armbian/os/actions/runs/9434613892 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 Per Igor comment helios64 required work to sync with upstream changes. I took the liberty to keep more of upstream than in Armbian 6.8, namely: I kept nodes at their upstream location to remove unnecessary work when syncing to the upstream keep "ethernet0 = &gmac;" in aliases, to let the ethernet MAC retrieved from OTP in u-boot apply. This will restore this feature (the u-boot was still functional). U-boot retried ethernet MACs are in u-boot printenv output "ethaddr" and "eth1addr". Seems for a few years I had the Linux kernel autogenerated one but my config still had the correct one commented (I did not find why it broke back then). I removed the overclock disabling code as the overclock is not included in the dts so no need to disable it (will lower the sync to upstream burden) kept upstream fix 93b36e1d3748c352a70c69aa378715e6572e51d1 "arm64: dts: rockchip: Fix USB interface compatible string on kobol-helios64" from upstream in vcc3v0_sd node I kept "enable-active-high;" and "gpio = <&gpio0 RK_PA1 GPIO_ACTIVE_HIGH>;" sync to upstream from helios64::status to helios64:green:status for system_leds : status_led kept startup-delay-us = <2000000> on hdd nodes from upstream (I believe they should not be the same value for rail a and b of the HDD, one should do as in the helios64 u-boot code where one is started after the other to lower the current load) I also did not sync with upstream the differences of gpio pull config for "power > sdmmc0_pwr_h" and "pinctrl > pmic > pmic_int_l" I kept the upstream DTS model "Kobol Helios64" instead of the armbian "Helios64". Ethernet rename from armbian-hardware-optimization works. Documentation summary for feature / change [ ] short restore ethernet MACs for eth0 read from OTP via u-boot [ ] This will restore the original intent which is to have the eth0 mAC be defined from the mainboard. This might affect MAC-based DHCP definitions [ ] ip l to get the Linux-defined eth0/end0 MAC, printenv in u-boot to see ethaddr and eth1addr for eth0/end0 and eth1 How Has This Been Tested? [ ] Compile, installed, and reboot, checked assigned IP was from the dnsmasq dhcp-host definition for this ethernet MAC. Did a few other reboots. 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

Description On every PR, a workflow is started to check if artifacts should be built. This happens not only once, but many times, e.g. for every selected reviewer. Since the workflow has cancel-in-progress enabled, workflows are started and immediately cancelled by the next one, resulting in many notifications (see https://github.com/armbian/build/actions/workflows/build-artifacts-pr.yml how many of the workflows were duplicates which were cancelled). Move the cancel-in-progress concurrency policy to the second job which starts only after a check is done if the 'Build' label is even active on the PR. This should greatly reduce "Workflow cancelled" notifications via GitHub and email (if enabled by the user). Documentation that concurrency can also be used on jobs: https://docs.github.com/en/actions/using-jobs/using-concurrency#example-using-concurrency-and-the-default-behavior Also don't start the workflow on PR 'reviewer_requested' trigger. It does not need to be started every time a single reviewer is added, since requesting a review does not change the build. If the 'Build' label was already added earlier, the build workflow will have been started already. In addition, don't run shellcheck if a PR message ot title was edited since it does not change the code at all. See doc: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=edited#pull_request How it has been tested [x] Check started workflow this PR: https://github.com/armbian/build/actions/workflows/build-artifacts-pr.yml 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 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. In theory, rk3588-legacy is also still <6.1, but that boot script is also used by 6.1 vendor kernel and the amount of new images being built/used with the 5.10 legacy kernel is likely minimal. As far as I know, bootscript won't update automatically, so these changes will only apply to freshly built images. Please correct me if I'm wrong. Link to kernel commit: https://github.com/torvalds/linux/commit/b25806dcd3d5248833f7d2544ee29a701735159f Closes issue https://github.com/armbian/build/issues/6633 Also, there are other kernel parameters, e.g.: cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory https://github.com/armbian/build/blob/d7db1cd26b926bff2b19193f6de30dbc1910aa20/config/bootscripts/boot-rockchip64.cmd#L42 I couln't find out why cgroup_enable= is added here. The official kernel parameters doc (https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-parameters.txt) only lists a cgroup_disable= option. Maybe this is some relic of the past? Does anyone know?` Is there a way to find out on a live kernel what the boot arguments actually did? Jira reference number AR-2321 View the full article

Description Support partner. How Has This Been Tested? [x] Was reported as working good. Checklist: [x] Any dependent changes have been merged and published in downstream modules View the full article

Description In an effort to reduce wifi driver burdens AR-1745, I went through the 6.10 kernel to check if any third party wifi drivers can be removed. The following drivers are part of the mainline kernel as of 6.10: RTL8723CS (driver: RTW88) RTL8811CU and RTL8821C (driver: RTW88) RTL8192EU (driver: RTL8XXXU) To give them some more time in the oven, use them not from 6.10 but from 6.11 onwards. I went through the Armbian forums, Atlassian and GiHub issues to see if anyone had used those drivers for these chips in the past and had reported issues. But I haven't found anything yet. RTL8723DS is also supported by RTW88, but I have not touched that driver since it is still required for the RockPi-S wifi to work properly as reported by @brentr Jira reference number AR-1745 How Has This Been Tested? [x] Build success: ./compile.sh BOARD=nanopc-cm3588-nas BRANCH=edge RELEASE=trixie EXPERT=yes KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no [ ] Mainline drivers should be tested LOOKING FOR TESTERS: Drivers for RTL8811CU, RTL8821C and RTL8192EU are available also in 6.9, so if you have a device with those chips, it would be very nice if you could test them with their respective kernel driver (RTW88 or RTL8XXXU). You may have to enable them in your board's kernel config. If you have a board with a RTL8723DS chip, please test the RTW88 driver. If RockPi-S is the only board which broken RTL8723DS driver, we could switch most other boards to RTW88 for this chip. 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