RSS Bot

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

kernel-debs: headers: hack/fix for 6.5-rc1's "tools/counter: Makefile: Remove lingering 'include' directories on make clean" kernel-debs: headers: hack/fix for 6.5-rc1's "tools/counter: Makefile: Remove lingering 'include' directories on make clean" introduced at https://github.com/torvalds/linux/commit/228354ed692faa08f40f2630658c0771f77da457 simply creating the dir solves it reported to author, let's hope for an -rc2 fix. better logging when DEBUG=yes (don't pass "-s"(ilent) to make clean) View the full article

Use multiple consecutive reads in rtw_sdio_read_port() to limit the number of bytes which are copied by the host from the card in one MMC/SDIO transfer. This allows receiving a buffer that's larger than the hosts max_req_size (number of bytes which can be transferred in one MMC/SDIO transfer). As a result of this the skb_over_panic error is gone as the rtw88 driver is now able to receive more than 1536 bytes from the card (either because the incoming packet is larger than that or because multiple packets have been aggregated). Disabled: 001-revert-rtw88-sdio-size-and-timout-to-rfc-v1.patch 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 Removed rtl8822cs bluetooth patches from sunxi patch directory to make use of patches from driver harness. Also in the process I noticed that rtl8822cs bluetooth patches were upstreamed in 5.18 and were unnecessarily applied on newer kernels. Added condition to prevent the same in driver-network.sh 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 legacy, current and edge allwinner images and tested them on nanopiduo2 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 When a hardware doesn't have video out, we set PLYMOUTH to no to determine if we our plymouth theme needs to be installed. But on the other hand, for standard images, even when PLYMOUTH is set to no we leave plymouth installed in the final image. This PR changes the same to make sure plymouth is not installed when its not needed. Reduces little bit of boot time and helps keep u-boot logs intact on serial console. 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 a image for nanopiduo2 as it doesn't have video output and made sure plymouth is not installed in standard image 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 tittle. How Has This Been Tested? Tested for patching only. 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 Jira reference number AR-1800 How Has This Been Tested? [x] Kernel compiles and image builds 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 As per subject, move rk322x edge kernel to 6.4 How Has This Been Tested? [x] Image compilation successful [x] Image successfully run on actual device 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 We call ssh-keygen when building with CRYPTROOT=yes, but openssh-client is not mentioned into EXTRA_BUILD_DEPS in extensions/fs-cryptroot-support.sh which can make the build to fail. This PR fixes the same 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] Created a build with CRYPTROOT=yes and ARTIFACT_IGNORE_CACHE=yes and made sure it no longer fails because of missing ssh-keygen in docker 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

Today, Imagination Technologies announced they are now using Zink for full OpenGL 4.6 support. This is the first time we've seen a hardware vendor trust Zink enough to completely side-step a native OpenGL driver and use it in a shipping product. View the full article

Description Code for ssv6051 wifi driver sometimes set RX_ENC_xxx flags in the 'flag' field in the ieee80211_rx_status object. These flags belong in the 'enc_flags' field. Setting them in 'flag' clashed with the RXX_FLAG_MMIC_ERROR bit, and caused the supplicant to report a spurious michael mic error and close the connection. How Has This Been Tested? Connects to my wireless access point now: did not do so before 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 These patches went missing sometime during development cycle of this release. Looks like they are needed for emmc support on nanopi neo core 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] Checked that u-boot builds and patches gets applied correctly 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

rk3588-legacy: add Mixtile Blade 3 mixtile-blade3.wip rk3588-legacy: add Mixtile Blade 3 mixtile-blade3.wip with it's own rockchip next-dev based u-boot and patches for PD View the full article

thinkpad-x13s: bump to steev's 6.4.y; fix for missing chroot_sdcard for add-apt-repository thinkpad-x13s: bump to steev's 6.4.y; update .config thinkpad-x13s: fix for missing chroot_sdcard for add-apt-repository call View the full article

debs: remove Installed-Size: 1 from control files; Installed-Size is properly calculated at fakeroot_dpkg_deb_build() for all packages debs: remove Installed-Size: 1 from control files; Installed-Size is properly calculated at fakeroot_dpkg_deb_build() for all packages View the full article

partitioning: declare global readonly ROOT_PART_UUID for later hooks partitioning: declare global readonly ROOT_PART_UUID for later hooks View the full article