RSS Bot

Based on the works done by @lanefu for the same RK3568 NanoPi R5S, with ethernet interface name updated and corresponding LED dtb overlay. Tested with a local built Armbian-unofficial_24.2.0-trunk_Nanopi-r5c_bookworm_edge_6.6.4_minimal.img on my NanoPi R5C: [✔️] Boot with SD card. [✔️] Install into eMMC and boot from eMMC. [✔️] LAN / WAN interface renamed and corresponding LEDs work with link status change. View the full article

Description version bump for rockchip-rk3588 edge from 6.7-rc3 to rc4. Jira reference number [-] How Has This Been Tested? [x] built on aarch64 for OPi5 From a quick look it does not seem that there are a lot of changes related to the board or even arm64 architecture in general. Therefore booting was not tested. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v6.7-rc4&id2=v6.7-rc3&dt=2 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

Our look at the Rust crate for interconnected objects continues, as we examine how persian-rug really does tie the room together by providing a convenient container solution with a safety net to go along with it. View the full article

Description Adjusting logic due to upstream changes https://github.com/actions/labeler/releases/tag/v5.0.0 How Has This Been Tested? [x] Tested on demo repository Checklist: [x] My code follows the style guidelines of this project [x] My changes generate no new warnings View the full article

Description Update odroidxu4-current kernel to 6.1.65. How Has This Been Tested? [x] Reboot of my Odroid HC1 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

Bumps actions/labeler from 4 to 5. Release notes Sourced from actions/labeler's releases. v5.0.0 What's Changed This release contains the following breaking changes: The ability to apply labels based on the names of base and/or head branches was added (#186 and #54). The match object for changed files was expanded with new combinations in order to make it more intuitive and flexible (#423 and #101). As a result, the configuration file structure was significantly redesigned and is not compatible with the structure of the previous version. Please read the action documentation to find out how to adapt your configuration files for use with the new action version. The bug related to the sync-labels input was fixed (#112). Now the input value is read correctly. By default, dot input is set to true. Now, paths starting with a dot (e.g. .github) are matched by default. Version 5 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. For more information, please read the action documentation. New Contributors @​joshdales made their first contribution in actions/labeler#203 @​dusan-trickovic made their first contribution in actions/labeler#626 @​sungh0lim made their first contribution in actions/labeler#630 @​TrianguloY made their first contribution in actions/labeler#629 Full Changelog: https://github.com/actions/labeler/compare/v4...v5.0.0 v5.0.0-beta.1 What's Changed In scope of this beta release, the structure of the configuration file (.github/labeler.yml) was changed from LabelName: - any: - changed-files: ['list', 'of', 'globs'] - base-branch: ['list', 'of', 'regexps'] - head-branch: ['list', 'of', 'regexps'] - all: - changed-files: ['list', 'of', 'globs'] - base-branch: ['list', 'of', 'regexps'] - head-branch: ['list', 'of', 'regexps'] to LabelName: - any: - changed-files: - AnyGlobToAnyFile: ['list', 'of', 'globs'] - AnyGlobToAllFiles: ['list', 'of', 'globs'] - AllGlobsToAnyFile: ['list', 'of', 'globs'] - AllGlobsToAllFiles: ['list', 'of', 'globs'] - base-branch: ['list', 'of', 'regexps'] - head-branch: ['list', 'of', 'regexps'] - all: - changed-files: - AnyGlobToAnyFile: ['list', 'of', 'globs'] - AnyGlobToAllFiles: ['list', 'of', 'globs'] - AllGlobsToAnyFile: ['list', 'of', 'globs'] </tr></table> ... (truncated) Commits 8558fd7 Merge pull request #709 from actions/v5.0.0-beta 000ca75 Merge pull request #700 from MaksimZhukov/apply-suggestions-and-update-docume... cb66c2f Update dist 9181355 Apply suggestions for the beta vesrion and update the documentation efe4c1c Merge pull request #699 from MaksimZhukov/update-node-runtime-and-dependencies c0957ad Run Prettier 8dc8d18 Update Node.js version in reusable workflows d0d0bbe Update documentation 1375c42 5.0.0 ab7411e Change version of Node.js runtime to node20 Additional commits viewable 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 We are using unudhcpd from pmos for usb gadget network dhcp server. But this package is not upstreamed to debian, and it's the only package we use for qcom abl that is not upstreamed, so replace it with dnsmasq. Difference between unudhcpd and dnsmasq: 1, unudhcpd is a very simple dhcp server which only provides one ip address to the client. While dnsmasq will provide different ip address on every usb gadget network connect because the mac address of usb gadget network client always changes. 2, When usbgadget network is disabled by command systemctl status usbgadget-rndis.service, dnsmasq will get stopped. If dnsmasq is not stopped, client won't get address next time usbgadget network is enabled. Also add slot_suffix arg to kernel cmdline because qbootctl need it to get current slot. 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 Enabled crust for Orange Pi Zero. Also added workaround to make sure board does resume successfully after sleep. The xradio_wlan driver seems to interfere with the same causing board to get stuck on resume after its put to sleep. Hence now we unload the module when entering sleep and reload it on resume. This works with systemctl suspend, but is still broken with rtcwake. Jira reference number AR-1918 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 suspend/resume works using echo +20 > /sys/class/rtc/rtc0/wakealarm && systemctl suspend 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 Current rockchip64 bootscript always load kernel/etc from the first device partition, but not from partition bootscript itself was loaded. This PR makes bootscript load kernel/etc from the same partition. This allows to easily have multiple boot partitions (primary/backup) and switch them with MBR boot flags or GPT legacy_boot flags. How Has This Been Tested? [x] Compile and boot rk3318-box 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per description. How Has This Been Tested? [ ] Build test Not tested on hardware. 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. [x] Someone tested with rock5 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 Bump from rc1 to rc3 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] build [x] boot on OPi5 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 We use mkbootimg in rootfs which is installed only for jammy before. It's better to use mkbootimg from build host because this is a python script and may not run if build host and target rootfs are not the same release. This commit only make build for debian pass, but debian images won't work because of lacking packages. 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 build BOARD=xiaomi-elish BRANCH=sm8250 BUILD_DESKTOP=no BUILD_MINIMAL=yes DEB_COMPRESS=xz EXPERT=yes GITHUB_MIRROR=ghproxy KERNEL_CONFIGURE=no KERNEL_GIT=shallow MAINLINE_MIRROR=tuna RELEASE=trixie 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 The latest ATF has several fixes and improvements for the K3 platform. The current default ATFBRANCH is rather old (and should be updated, but I don't have all the other platforms needed to test right now). For now update to the latest stable tag for K3 platforms. How Has This Been Tested? [ ] Build and boot SK-AM64B [ ] Build and boot SK-AM62B [ ] Build and boot SK-TDA4VM 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 On older kernels like v6.1.x the TI devices are better supported by the TI vendor kernel than the upstream kernel. For the current kernel let's use the TI kernel for these boards. While here bump the edge kernel to v6.6.x which also has better support for features found on these platforms than v6.5.x. How Has This Been Tested? [x] Build and boot SK-AM64B with current kernel [ ] Build and boot SK-AM62B with current kernel [x] Build and boot SK-TDA4VM with current kernel [x] Build and boot SK-AM64B with edge kernel [ ] Build and boot SK-AM62B with edge kernel [ ] Build and boot SK-TDA4VM with edge kernel 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

The testing ecosystem in the Linux kernel has been steadily growing, but are efforts sufficiently coordinated? How can we help developers and maintainers integrate code more efficiently? How can we mitigate maintainer burnout? View the full article

The 3rd revision of the patch has been applied upstream. https://lore.kernel.org/linux-wireless/87cyvqsabo.fsf@kernel.org/T/#t I've been using this revision for about week now and all seems fine. 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 Resolves #5890 Jira reference number AR-1906 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] Test on RPi5 with mantic image. The iwconfig shows output shows that power management is off 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 Moving use of dbeinder's repo to fifteenhex repo for xradio driver as fifteenhex seems to give more consistent speeds. This also allows us to drop all of our xradio patches as we can now build right from fifteenhex code. 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] Test wifi on Orange Pi Zero 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 Add support for RPi5 in our bcm2711 kernel. This is mostly but not entirely based on changes from Raspberry Pi kernel PR 5618. After enabling those options, I noticed that even though hdmi was working, kernel was not able to find the sdcard and usb was also not working. So I had to use diffconfig to compare our configs with the vendor config and enable some more options. Raising the PR so that others can also play with it as well. Meanwhile I will work on getting Trixie Desktop Image running with mesa 23.3-rc5 from experimental repo. As part of that I will split RPi 5 into separate board config until recent version of mesa is made available in current debian or ubuntu distributions's backport repositories. 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 by creating Mantic cli image. HDMI works, wifi works, ethernet is detected but I haven't tested if it works, usb 2 works, haven't tested usb3. 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 This was going to be used if building the bootloader from external source did not work. As this did work we never needed this blob, remove it. How Has This Been Tested? [x] SK-AM62B still builds and boots without this file Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description thead: fix bluetooth problem, update to linux 6.7-rc3 Add RTL bluetooth firmware for LicheePi 4A. Update prebuilt opensbi binary. Update linux version and kernel config(fix SD-slot, cpufreq). 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 [ ] 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

No descriptionView the full article

Description Maint. View the full article

Description Enabled CONFIG_RCU_TRACE as a workaround to fix booting 6.1.64 kernel on 32-bit allwinner boards. Edge kernel is not having this issue and hence workaround was not added for 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] Booted on Orange Pi Zero (sun8i H3) 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