RSS Bot

Description The kernel build fails with: [🐳|🔨] drivers/net/wireless/rtl88x2bu/os_dep/linux/wifi_regd.c: In function 'rtw_regd_init': [🐳|🔨] drivers/net/wireless/rtl88x2bu/os_dep/linux/wifi_regd.c:409:36: error: 'REGULATORY_IGNORE_STALE_KICKOFF' undeclared (first use in this function) [🐳|🔨] 409 | wiphy->regulatory_flags |= REGULATORY_IGNORE_STALE_KICKOFF; [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] drivers/net/wireless/rtl88x2bu/os_dep/linux/wifi_regd.c:409:36: note: each undeclared identifier is reported only once for each function it appears in [🐳|🔨] make[6]: *** [scripts/Makefile.build:252: drivers/net/wireless/rtl88x2bu/os_dep/linux/wifi_regd.o] Error 1 note that this bug only affect >= 6.3.13 < 6.4 and >=6.5-rc1 as of the 16th of July 2023. Cope with the fix in stable 6.3.13 bf353116d1bf and 6.5-rc1 e8c2af660ba0 "wifi: cfg80211: fix regulatory disconnect with OCB/NAN". That is the removal of REGULATORY_IGNORE_STALE_KICKOFF from the wireless regulator internal API to fix any driver that allowed OCB/NAN. This code will need to be expanded once and if 6.4 include the above fixup. 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] 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=helios64 BRANCH=edge RELEASE=bookworm BUILD_ONLY="kernel" KERNEL_CONFIGURE=no BUILD_KSRC=no No runtime tested. My hardware is currently in a test so I cannot reboot in the new kernel. Also I do not have this wireless device so I cannot test this driver code works correctly either way. Checklist: [ ] 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 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] 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: [ ] 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 Enable the DLN2 driver for support the USB IO board View the full article

Description Enable power led in u-boot on H5 based boards. 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] Booted on Orange Pi Prime 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

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

Update maintainers synched from the database View the full article

Update maintainers synched from the database View the full article

Update maintainers synched from the database View the full article

Description Removed Allwinner spi patch for u-boot. It was upstreamed in 2018 and is currently available as SPI_SUNXI config option in u-boot. Also it looks like driver added by the removed patch was never enabled for any of the boards. Hence removing it also doesn't makes any difference for that reason either. 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 Adding myself as the maintainer for Orange Pi Prime board. Also changed crust config for this board to be more board specific. 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] Booted on Orange Pi Prime 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 Lets wait for upstream to be updated for 6.3, 6.4 and up. How Has This Been Tested? [x] Build test Checklist: [x] My changes generate no new warnings View the full article

With Black Valley in Norway, and Akademy in Greece, this weekend's plans are all set or computer enthusiasts! Collabora is proud to sponsor both of these events as a chance for communities to come together and strengthen their bonds. View the full article

Added shell.nix definition for temporary development environment for Nix(OS) Set uuidgen and other binaries check to not rely on hard-codded paths 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] 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] On NixOS 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

Adjusted patching in drivers/net/wireless/realtek/rtw88/usb.c to reflect update in Linux 6.3.13 (EOL) https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/net/wireless/realtek/rtw88/usb.c?id=v6.3.13&id2=v6.3.12 [ ] 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

mixtile-blade3: bump rk3588 blobs: DDR to 1.11 and BL31 to 1.38 mixtile-blade3: bump rk3588 blobs: DDR to 1.11 and BL31 to 1.38 tested on actual board, works perfectly View the full article

RFC: rockpro64: blobless with 2.8.5 ATF, 2023.01 u-boot RFC: rockpro64: blobless with 2.8.5 ATF, 2023.01 u-boot 2023.04 fails during USB init, thus using 23.01 (23.07 untested) blobless with newer 2.8.5 ATF the previous problems with PCIe are not totally solved by this View the full article

armbian-desktop/aggregation: introduce DESKTOP_COMMON aggregation variant, where arch/config/appgroups are ignored; see #5439 armbian-desktop/aggregation: introduce DESKTOP_COMMON aggregation variant, where arch/config/appgroups are ignored; see #5439 View the full article

uboot: allow adding/changing uboot CFLAGS with post_config_uboot_target() hook uboot: allow adding/changing uboot CFLAGS with post_config_uboot_target() hook View the full article

u-boot-menu: allow avoid using uInitrd, for when the bootloader requires modern initrd.img u-boot-menu: allow avoid using uInitrd, for when the bootloader requires modern initrd.img View the full article

drivers-harness: add branch to drivers base cache key declare cache_key_base="${KERNEL_MAJOR_MINOR}_${LINUXFAMILY}_${BRANCH}" drivers-harness: add branch to drivers base cache key declare cache_key_base="${KERNEL_MAJOR_MINOR}_${LINUXFAMILY}_${BRANCH}" this allows for 2 branches with the same version to not interfere with each other View the full article

partitioning: declare global readonly ROOT_PART_UUID for later hooks partitioning: declare global readonly ROOT_PART_UUID for later hooks re-use local root_part_uuid instead of running blkid multiple times View the full article

Description Bumped the Allwinner kernel and U-boot U-boot - 2023.07-rc6 -> 2023.07 Legacy - 5.15.119 -> 5.15.120 Current - 6.1.37 -> 6.1.38 Edge - 6.4.1 -> 6.4.2 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 and booted on NanoPi Duo2 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 When booting on H3 boards with regulator-gpio, we get the following error. [ 8.518147] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518188] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 8.518373] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518391] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 8.518565] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.518585] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 8.518752] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.518770] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 9.016159] thermal_sys: Failed to bind 'cpu_thermal' with 'cpufreq-cpu0': -22 [ 9.016200] thermal_sys: Failed to bind 'cpu_thermal' with 'cpufreq-cpu0': -22 These boards have the voltage capped at 1.3Volts and can't support voltages higher than that. Because of that we get reduced from having 8 cpufreq states to just 4 states that further causes us to observe the error thrown by thermal_sys module. This PR fixes the same. Also I have disabled 1.368 Ghz operation state as in my test, my board hit the first trip in just 1 sec throttling the board down to 1.296 Ghz instantaneously. If anyone needs the same, we do have the overclock overlay for that anyway. Also enabled legacy kernel for NanoPi Duo2. 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 that patch applies on legacy, current as well as edge kernel [X] Booted on NanoPi Duo2. Made sure error related to thermal_sys is not shown in dmesg. Also ran minerd --benchmark and monitored the system with armbianmonitor -M to make sure trips are working as expected. 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Some people is complaining in the forums, thus it is better to revert this back to 333mhz How Has This Been Tested? [x] kernel and image compilation works 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 ：） How Has This Been Tested? 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