RSS Bot

Description We have an arg UBOOT_MIRROR and it can be set to gitee to use mirror https://gitee.com/mirrors/u-boot.git. We have to fix Makefile url for it. 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] PREFER_DOCKER=no ./compile.sh uboot BOARD=fl700n BRANCH=edge UBOOT_MIRROR=gitee. fl700n is a board using uboot config firefly-rk3288_defconfig I am playing these days. 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

With many dedicated souls willing to endure a FOSDEM queue, Collabora's engineers will be giving 6 talks spread out amongst multiple devrooms including Open Media and Testing & Continuous delivery. View the full article

PWM controllable fan (G12A/B/SM1) Commit provides two new overlays. One for the BananaPi CM4IO Baseboard "GPIOH_5" and another for general use "GPIOX_5". CM4IO HEADER PINS: 5V "4"; GND "6"; PWM "7" On other units the location of the PWM HEADER PIN may vary, so users will need to either review the wiki or schematic of said unit. Fan used in testing: https://a.co/d/hasnLtj Modifications: M2S/M5 RTL8822CS Modded the overlays to be specific to the unit they were made to be used on. Tested-on: BananaPi BPI-CM4IO Baseboard with BPI-CM4 Module [ ] 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 [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Fix compilation of the uwe5622 driver with fortify enabled. Currently I get the following error: [🔨] In function 'strncpy', [🔨] inlined from 'sprdwl_cfg80211_scan' at drivers/net/wireless/uwe5622/unisocwifi/cfg80211.c:1541:4: [🔨] ./include/linux/fortify-string.h:144:17: error: call to '__write_overflow' declared with attribute error: detected write beyond size of object (1st parameter) [🔨] 144 | __write_overflow(); [🔨] | ^~~~~~~~~~~~~~~~~~ [🔨] make[8]: *** [scripts/Makefile.build:243: drivers/net/wireless/uwe5622/unisocwifi/cfg80211.o] Error 1 It seems that fortify considers the 0 sized array at the end of the struct as actually being 0 sized rather than it's pre-C99 meaning of undefined size array. This patch changes to the standard C99 representation of undefined size array at end of struct. How Has This Been Tested? Compilation of the rockchip64-edge kernel (6.7). 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 [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per title + leave defaults as is. Jira reference number AR-2027 How Has This Been Tested? [x] Making one image 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

One of the key high-level challenges of building Mesa drivers these days is figuring out how to best share code between a Vulkan driver and a Gallium driver when Gallium isn't really capable of implementing Vulkan. Here's how. View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description Status change. View the full article

Bumps actions/upload-artifact from 4.0.0 to 4.1.0. Release notes Sourced from actions/upload-artifact's releases. v4.1.0 What's Changed Add migrations docs by @​robherley in actions/upload-artifact#482 Update README.md by @​samuelwine in actions/upload-artifact#492 Support artifact-url output by @​konradpabjan in actions/upload-artifact#496 Update readme to reflect new 500 artifact per job limit by @​robherley in actions/upload-artifact#497 New Contributors @​samuelwine made their first contribution in actions/upload-artifact#492 Full Changelog: https://github.com/actions/upload-artifact/compare/v4...v4.1.0 Commits 1eb3cb2 Merge pull request #497 from actions/robherley/update-readme-limit 8688a86 Update readme to reflect new artifact/job limit 73d8b66 Support artifact-url output (#496) c320f57 Update README.md (#492) cf8714c Merge pull request #482 from actions/robherley/add-migration-docs 7f16e37 add migrations docs 3530730 Merge pull request #468 from actions/robherley/misc-updates 6c139af update imports and old v4-beta references See full diff 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 Allow to disable boot partition by explicit BOOTSIZE=0. This would help when bootloader known to support rootfs FS. Allow image_size < rootfs_size for (potentially compressed) btrfs. 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 compressed btrfs-rootfs image with FIXED_IMAGE_SIZE=$((rootfs_size/2)) and without boot partition Checklist: [ ] 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 [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description There is an orbiting patch that adds True Random Number Generator (TRNG) completing the rockchip mainline crypto driver. This PR introduces the patch (which is in RFC condition, thus passible of changes) with these benefits: provides better entropy (see below) removes the memory region claim error in dmesg is almost in mainline Some caveats: the existing driver covers rk3288 (32 bit, not applicable in this context), rk3328 and rk3399, but only rk3399 seems to have working hardware. For the other two chips, the TRNG is just disabled. How Has This Been Tested? [x] Current 6.6 kernel packages built and installed on live system (rk3399) [x] Edge 6.7 kernel packages built and installed on live system (rk3399) dmesg can be used to verify if TRNG is enabled: [ 8.091984] rk3288-crypto ff8b0000.crypto: will run requests pump with realtime priority [ 8.092031] rk3288-crypto ff8b0000.crypto: Register ecb(aes) as ecb-aes-rk [ 8.092077] rk3288-crypto ff8b0000.crypto: Register cbc(aes) as cbc-aes-rk [ 8.092087] rk3288-crypto ff8b0000.crypto: Register ecb(des) as ecb-des-rk [ 8.092098] rk3288-crypto ff8b0000.crypto: Register cbc(des) as cbc-des-rk [ 8.092107] rk3288-crypto ff8b0000.crypto: Register ecb(des3_ede) as ecb-des3-ede-rk [ 8.092116] rk3288-crypto ff8b0000.crypto: Register cbc(des3_ede) as cbc-des3-ede-rk [ 8.092126] rk3288-crypto ff8b0000.crypto: Register sha1 as rk-sha1 [ 8.092137] rk3288-crypto ff8b0000.crypto: Register sha256 as rk-sha256 [ 8.092146] rk3288-crypto ff8b0000.crypto: Register md5 as rk-md5 [ 8.092156] rk3288-crypto ff8b0000.crypto: Register TRNG with sample=1200 The mail in the kernel mailing list provides some insight and instruction on how to prove effectiveness of the RNG. Testing existing driver provided by vendor kernel looks quite ineffective in providing decent randomness: root@orangepi4-lts:~# cat /sys/devices/virtual/misc/hw_random/rng_current rockchip root@orangepi4-lts:~# dd if=/dev/hwrng count=100 bs=2048 | rngtest rngtest 2.2 Copyright (c) 2004 by Henrique de Moraes Holschuh This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. rngtest: starting FIPS tests... rngtest: entropy source exhausted! rngtest: bits received from input: 1638400 100+0 records in 100+0 records out rngtest: FIPS 140-2 successes: 0 rngtest: FIPS 140-2 failures: 81 rngtest: FIPS 140-2(2001-10-10) Monobit: 3 rngtest: FIPS 140-2(2001-10-10) Poker: 81 rngtest: FIPS 140-2(2001-10-10) Runs: 81 rngtest: FIPS 140-2(2001-10-10) Long run: 0 rngtest: FIPS 140-2(2001-10-10) Continuous run: 0 rngtest: input channel speed: (min=528.429; avg=1086.773; max=1379.618)Kibits/s rngtest: FIPS tests speed: (min=14.341; avg=47.788; max=59.051)Mibits/s 204800 bytes (205 kB, 200 KiB) copied, 1.52111 s, 135 kB/srngtest: Program run time: 1522960 microseconds While the mainline patch adjusts the number of samples and, albeit being slower and not high quality, seems to be better: root@orangepi4-lts:~# dd if=/dev/hwrng count=100 bs=2048 | rngtest rngtest 2.2 Copyright (c) 2004 by Henrique de Moraes Holschuh This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. rngtest: starting FIPS tests... rngtest: entropy source exhausted! rngtest: bits received from input: 1638400 100+0 records in 100+0 records out rngtest: FIPS 140-2 successes: 28 rngtest: FIPS 140-2 failures: 53 rngtest: FIPS 140-2(2001-10-10) Monobit: 52 rngtest: FIPS 140-2(2001-10-10) Poker: 13 rngtest: FIPS 140-2(2001-10-10) Runs: 3 rngtest: FIPS 140-2(2001-10-10) Long run: 0 rngtest: FIPS 140-2(2001-10-10) Continuous run: 0 204800 bytes (205 kB, 200 KiB) copied, 7.31521 s, 28.0 kB/s rngtest: input channel speed: (min=131.364; avg=222.220; max=278.743)Kibits/s rngtest: FIPS tests speed: (min=17.628; avg=30.777; max=76.600)Mibits/s rngtest: Program run time: 7316184 microseconds Since the original driver from vendor kernel looks like quite useless, I would like to remove this and this soon from the patch archives, and perhaps adapt the mainline driver to provide RNG for rk3308 too, although it is probably useless since the hardware seems to be ineffective on rk3328 (see patch comments) and probably rk3308 is in the same league. @brentr what do you think about? 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder patch is slightly different for 2024.01 View the full article

wsl2: vhd/vhdx exts; more wsl2 kernel stuff linux-wsl2-x86-edge.config: enable moar Hyper-V stuff & console as builtin extensions: image-output-vhd renamed to image-output-vhd-azure only Azure wants the static, 1024-aligned original VHD images (and doesnt support VHDX?) new VHDX output format (for generic Hyper-V on Windows 10/11/2019/etc) extensions: image-output-vhdx: add output for dynamic .vhdx (in a zip file, to avoid sparseness errors) new VHDX output format (for generic Hyper-V on Windows 10/11/2019/etc) it is always stored (no compression) in a .zip file, to avoid sparseness errors when building, transfer the .zip file over to Windows, and uncompress it there (not on WSL2 itself/Linux/other machine) wsl2: enable image-output-vhdx for all wsl2 images (this enables wsl2 images to be run directly on Hyper-V) future work: export the rootfs .tar.gz, that can be used on WSL2 as a Custom Distro View the full article

bcm2711: switch to 48-bit virtual address; enable "docker optimizations" bcm2711-edge: switch to 48-bit virtual address; enable eBPF stuff & BTF for tcmalloc (enjoy, cilium, etc) stuff https://github.com/cilium/cilium/issues/23640 see https://github.com/libbpf/libbpf#bpf-co-re-compile-once--run-everywhere bcm2711-current: switch to 48-bit virtual address; enable eBPF stuff & BTF for tcmalloc (enjoy, cilium, etc) stuff https://github.com/cilium/cilium/issues/23640 see https://github.com/libbpf/libbpf#bpf-co-re-compile-once--run-everywhere bcm2711: cmdline.txt: enable "docker optimizations" most u-boot based boards get cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 by default (so work with docker/containerd/k8s/etc) View the full article

meson64: 6.7 edge: real bump to 6.7 meson64: 6.6 current: added -spidev DT's for a few boards & cleanup 0000.patching_config.yaml gives access to SPI Flash in exchange for slower eMMC cleanup 0000.patching_config.yaml for meson64-6.6 meson64: 6.7 edge: copy patches from 6.6 meson64: 6.7 edge: rebase patches to 6.7 general-rc-drivers-should-produce-alternate-pulse-and-space-timing-events.patch: dropped added -spidev DT's for a few boards (gives access to SPI Flash in exchange for slower eMMC) cleanup 0000.patching_config.yaml for meson64-6.7 meson64: 6.7 edge: fix SPI-NOR patch for 6.7.y general-spi-nor-add-support-for-XT25F128B.patch: fixed same as Paolo did for rockchip64-6.7 View the full article

Description Forgot to shift kernel configs for rockchip family when switching current to 6.6 and edge 6.7; done right now. Curiously I noticed this after hitting "buggy" behaviour on rk322x board with several rcu_scheduler debug messages while board was under high load, vnstatd process was often at 100% cpu usage and reading /proc/net/dev file (which is a simple text file with some network interface stats) stalls vnstatd. Turning off eth0 interface solved the problem but of course it was not solution. I shifted the kernel config, recompiled kernel 6.6 and this apparently solved the problem (maybe thanks to CONFIG_NEED_SRCU_NMI_SAFE=y ?) If it is so, the consideration I make here is that using that using a kernel config that does not match the kernel version may, in some corner cases, be harmful for stability How Has This Been Tested? [x] Kernel deb packages compiled and tested on live rk322x system 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

See the discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/3/#comment-179040 Description The Helios64-specific changes get moved to rockchip64, as https://github.com/armbian/build/blob/main/config/boards/helios64.csc#L3 says that it's not rk3399 anymore. How Has This Been Tested? See discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Ubuntu variants were somehow forgotten when adding systemd-resolved in https://github.com/armbian/build/pull/6142 Jira reference number AR-1657 How Has This Been Tested? [x] Generating Ubuntu Jammy image Checklist: [ ] 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 [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per subject: bump rockchip64 current kernel to 6.6 and edge kernel to 6.7 Jira reference number AR-2017 How Has This Been Tested? [ ] Compile kernel deb packages for 6.6 [ ] Compile kernel deb packages for 6.7 [ ] Build image and test with kernel 6.7 for rk3328 board [ ] Build image and test with kernel 6.7 for rk3399 board 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] I have made corresponding changes to the documentation [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 new borad of ASUS Tinker-Edge-R. ASUS Tinker Edge R is an Single Board Computer (SBC) specially designed for AI applications. I've written the device tree file for it, added the u-boot config file, and I've done the current version adaptation. Jira reference number [AR-9999] How Has This Been Tested? [x] UART test. The serial port output is printed through UART, and there are almost no errors in the armbian boot log. [x] Stability testing. Let the CPU run the specified task all the time, and the test will be conducted for 48 hours without any error. 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 [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description rtl8723cs driver need some little changes to compile on kernel 6.7; it was breaking rockchip and allwinner families This pull request contains those changes. Jira reference number AR-2025 How Has This Been Tested? [x] Patch applies correclty on kernel 6.7 [x] Kernel deb packages correctly built 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Collabora's kernel team made a number of key contributions including a new kselftest for verifying driver probe of Devicetree-based platforms, multiple improvements to further improve support for MediaTek SoCs found in Chromebooks, and more. View the full article

Description Bump all mainline based kernels. How Has This Been Tested? [ ] Build test within CI Checklist: [x] My code follows the style guidelines of this project [ ] My changes generate no new warnings View the full article

Create a overlay_prefix to h616 for orangepizero3. Description There are no overlays nor fixup scripts for h618. Since the orangepizero3 is i/o hardware identical to the orangepizero2, it makes sense to just point the zero3 to the zero2 overlays. Jira reference number [AR-9999] How Has This Been Tested? An image for orangepizero3 with this change was generated. It ran the fixup script on boot. Armbian-config -> System-> Hardware was used to enable an spidev. On reboot the overlay was loaded. 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] I have made corresponding changes to the documentation [ x] My changes generate no new warnings [ x] Any dependent changes have been merged and published in downstream modules View the full article