RSS Bot

Description Hello all, This PR adds support for the Texas Instruments SK-TDA4VM. Features, schematics, and purchase links can be found on the board page[0]. Notable features: 4GB LPDDR4‐4266 with support for inline ECC DisplayPort (v1.4) 4K resolution with MST support and HDMI Two CSI-2 ports compatible with Raspberry Pi 8 TOPS deep learning performance and hardware-accelerated edge AI Three USB 3.0 Type A ports, one USB 3.0 Type C port Gigabit Ethernet and 4x CAN-FD Headers M.2 Key E and M.2 Key M connectors Thanks! [0] https://www.ti.com/tool/SK-TDA4VM Depends on #5686 How Has This Been Tested? [x] Build/Boot tested Bookworm CLI/Minimal on Current(v6.1) and Edge(v6.5) kernels [x] Build/Boot tested Jammy CLI/Minimal on Current(v6.1) and Edge(v6.5) kernels [x] Gbit Ethernet works [x] HDMI works [x] USB 3.0 ports work 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

The latest mainline Linux kernel (v6.5) includes 22 patches that enable support for the AV1 uAPI and for two stateless video decoders: one for the Rockchip RK3588 and one for MT8195, a MediaTek SoC. View the full article

Linux 6.4.15 / 6.5.2 Remove duplicate label and correct goto err_release_hw placement. drivers/net/wireless/realtek/rtw88/usb.c: In function ‘rtw_usb_probe’: drivers/net/wireless/realtek/rtw88/usb.c:878:1: error: duplicate label ‘err_free_rx_bufs’ 878 | err_free_rx_bufs: 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

Work in progress, submitted for brainstorm and coordination prior to merge request and stuff Peer-reviews appreciated just don't treat it as ready to merge thing, most of the stuff are my tags to figure out :p View the full article

Description Update K3 edge Linux kernel to v6.5 and U-Boot to v2023.10-rc3. Plus a couple minor cleanup patches to k3.conf How Has This Been Tested? [x] Build and boot on SK-AM64B [x] Build and boot on SK-AM62B 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 mainline devicetree for opi3b 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] branch edge kernel build okay [x] kernel boots on opi3b 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 This PR partially reverts #5677 that I raised and merged today. I was able to get in touch with Samuel Holland and he suggested a fix for the network slowness issue which worked fine for current and edge. The fix doesn't seem to make a difference for legacy, but then the driver in legacy seems to be some early version of the driver that got merged in mainline. Hence I am leaving the driver disabled for legacy, while re-enabling the driver for current and edge with his proposed fix. Jira reference number AR-1833 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 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Bump crust to v0.6. Doesn't change anything for us other than version shown on serial console and dmesg log as the commits that went in from what we were using only includes 2 defconfig changes and some changes in readme file. 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 crust builds and works as expected on Nanopiduo2 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 This problem was first reported by a user on Armbian forum affecting Orange Pi Win and Orange Pi Prime with 6.1 kernel. The problem was when running iperf3 for network testing, it reported extremely low speed in the range of 40Mbps instead of 900Mbps that was shown on Debian kernel. It was also observed on multiple other devices during testing of 6.5 including Orange Pi Zero Plus by @schwar3kat and Pine A64+ by @PanderMusubi. Legacy kernel performed a bit better giving 400+ Mbps speed. Running something like htop or watch -n 1 echo in parallel seemed to resolve the issue. I was able to narrow it down to sun8i-a33-mbus driver which is dram frequency scaling driver for H5 and A64. It claims to support a33 to H3 as well, but I don't see the device tree compatible string for them in the driver code. Manually changing governor or min_freq in sysfs seems to get the speed back up. But when I tried changing the code ( it was just one variable value), the higher dram speed on reboot didn't solved the issue. Hence as a workaround, I am disabling this driver to bring back the speed. Disabling this driver also speeds up rendering on uart. Previously, when running neofetch it used to take about 5 seconds to render on my Orange Pi Prime, but now it renders in a fraction of second. After disabling this driver, the speed shown by iperf3 on legacy kernel is also up from previously reported 400Mbps to 900Mbps. Jira reference number AR-1833 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 on Orange Pi Prime (sun50i H5) 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

Bumps actions/checkout from 3 to 4. Release notes Sourced from actions/checkout's releases. v4.0.0 What's Changed Update default runtime to node20 by @​takost in actions/checkout#1436 Support fetching without the --progress option by @​simonbaird in actions/checkout#1067 Release 4.0.0 by @​takost in actions/checkout#1447 New Contributors @​takost made their first contribution in actions/checkout#1436 @​simonbaird made their first contribution in actions/checkout#1067 Full Changelog: https://github.com/actions/checkout/compare/v3...v4.0.0 v3.6.0 What's Changed Mark test scripts with Bash'isms to be run via Bash by @​dscho in actions/checkout#1377 Add option to fetch tags even if fetch-depth > 0 by @​RobertWieczoreck in actions/checkout#579 Release 3.6.0 by @​luketomlinson in actions/checkout#1437 New Contributors @​RobertWieczoreck made their first contribution in actions/checkout#579 @​luketomlinson made their first contribution in actions/checkout#1437 Full Changelog: https://github.com/actions/checkout/compare/v3.5.3...v3.6.0 v3.5.3 What's Changed Fix: Checkout Issue in self hosted runner due to faulty submodule check-ins by @​megamanics in actions/checkout#1196 Fix typos found by codespell by @​DimitriPapadopoulos in actions/checkout#1287 Add support for sparse checkouts by @​dscho and @​dfdez in actions/checkout#1369 Release v3.5.3 by @​TingluoHuang in actions/checkout#1376 New Contributors @​megamanics made their first contribution in actions/checkout#1196 @​DimitriPapadopoulos made their first contribution in actions/checkout#1287 @​dfdez made their first contribution in actions/checkout#1369 Full Changelog: https://github.com/actions/checkout/compare/v3...v3.5.3 v3.5.2 What's Changed Fix: Use correct API url / endpoint in GHES by @​fhammerl in actions/checkout#1289 based on #1286 by @​1newsr Full Changelog: https://github.com/actions/checkout/compare/v3.5.1...v3.5.2 v3.5.1 What's Changed Improve checkout performance on Windows runners by upgrading @​actions/github dependency by @​BrettDong in actions/checkout#1246 New Contributors @​BrettDong made their first contribution in actions/checkout#1246 ... (truncated) Changelog Sourced from actions/checkout's changelog. Changelog v4.0.0 Support fetching without the --progress option Update to node20 v3.6.0 Fix: Mark test scripts with Bash'isms to be run via Bash Add option to fetch tags even if fetch-depth > 0 v3.5.3 Fix: Checkout fail in self-hosted runners when faulty submodule are checked-in Fix typos found by codespell Add support for sparse checkouts v3.5.2 Fix api endpoint for GHES v3.5.1 Fix slow checkout on Windows v3.5.0 Add new public key for known_hosts v3.4.0 Upgrade codeql actions to v2 Upgrade dependencies Upgrade @​actions/io v3.3.0 Implement branch list using callbacks from exec function Add in explicit reference to private checkout options [Fix comment typos (that got added in #770)](actions/checkout#1057) v3.2.0 Add GitHub Action to perform release Fix status badge Replace datadog/squid with ubuntu/squid Docker image Wrap pipeline commands for submoduleForeach in quotes Update @​actions/io to 1.1.2 Upgrading version to 3.2.0 v3.1.0 Use @​actions/core saveState and getState Add github-server-url input v3.0.2 Add input set-safe-directory v3.0.1 ... (truncated) Commits 3df4ab1 Release 4.0.0 (#1447) 8b5e8b7 Support fetching without the --progress option (#1067) 97a652b Update default runtime to node20 (#1436) 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 A change to ledtrig_netdev driver causes the boot to fail on Orangepi-r1plus-lts and possibly other boards. The board boots and LED netdev trigger works if service is modified to occur later in the boot sequence by using After=timers.target in armbian-led-state.service. Jira reference number AR-1875 Issue discussion rockchip64: bump rockchip64-edge kernel to 6.5#5657 How Has This Been Tested? Tested on current and 6.5y Rockchip64 and other (H5). The following configurations were tested for boot, reboot and shutdown then boot and that LED's light when network is connected and LED's flicker on network activity: [x] Orangepi R1 Plus LTS with Kernel 6.5y with ledtrig_netdev configured for two ethernet ports and two LED's. [x] Orangepi R1 Plus LTS with Kernel 6.1y with ledtrig_netdev configured for two ethernet ports and two LED's. [x] Orangepi Zero Plus with Kernel 6.5y with ledtrig_netdev configured for one ethernet ports and one LED. 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 With this change, it is possible to select the collabora branch and build it on a Radxa Rock 5A. How Has This Been Tested? In Ubuntu on an x64 CPU, I have run ./compile.sh, selected the Rock-5a wip product, and then selected the collabora branch. I built if with desktop (which is overkill of course), but it boots nicely to Linux. I was allowed to setup my own user and the Ethernet port works nicely. uname -a Linux rock-5a 6.5.0-rc1-collabora-rockchip-rk3588 #1 SMP PREEMPT_DYNAMIC Fri Jul 28 15:49:06 UTC 2023 aarch64 GNU/Linux lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 006 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 Bumped legacy, current and edge kernel. Legacy - 5.15.127 -> 5.15.130 Current - 6.1.47 -> 6.1.51 Edge - 6.5 -> 6.5.1 Fixed compilation of xradio and as its working fine, disabled cw1200 driver that I added for edge last week. Refreshed kernel configs. Also uwe5622 patches needed for orange pi 3 lts were not being applied as least kernel version was set to 6.0. Moved it back to 5.15. Not sure if it works though will test next week once I receive my orangepi 3 lts. Also for edge kernel, enabled rtw88 based drivers and disabled their corresponding legacy counterparts. 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 all images on NanoPi Duo2 (sun8i H3) [X] Tested all images on Orange Pi Prime (sun50i H5) [X] Tested xradio drivers on Orange Pi Zero 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 Board info: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-3B.html Devicetree and uwe5622 driver is in this pr: https://github.com/armbian/linux-rockchip/pull/88 I've written a mainline devicetree but since we are bumping rockchip64-edge to 6.5, I will add it later. 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] legacy build success [x] legacy build boot fine on opi3b 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 Enable rockchip rkisp module for rockchip64 boards in edge. There has been driver support upstreamed into the kernel but it is not compiled for the rockchip64 kernels. https://docs.kernel.org/admin-guide/media/rkisp1.html 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] Compiled edge 6.4.12 on rockpi 4c with modules enabled and it boots. Modules have not been enabled in device trees yet (I haven't done the work yet but hope to PR these) 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

Description This is the generic default and should not have this postfix. How Has This Been Tested? [x] When ATFDIR is not set, the default directory is called simply "arm-trusted-firmware" 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Seems updates to all but the first extension hooks were not causing a rebuild, looks like the hash function dumper only looks at the first argument, but it is passed in a list of functions to dump in every call site. @rpardini , Does this look right? My BASH skills still need some work :smile: How Has This Been Tested? [x] Before this patch, make change to extension function (like fetch_custom_uboot) see that U-Boot is not regenerated [x] Make same change after applying this patch and see it now does get regenerated 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 The causes the first-stage bootloader to be generated before the normal U-Boot allowing the later build to use the firmware fetched during the first-stage build. How Has This Been Tested? [x] Boot SK-AM62B 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 This however only works for selected monitors with 1920x1080 and 4K resolutions. Also display seems to render extremely slowly. If the monitor is turned off and then on or is disconnected and reconnected while Armbian is running, monitor is not detected until a device reboot is performed. All of these however seems to be Khadas's kernel/u-boot limitations 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 attaching vim1s to samsung's 1920x1080 monitor [X] Rpardini tested on 4k display 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

rk3568-odroid/edge: bump to 6.5.y from -rc6; rebase all patches vs v6.5(.0) rk3568-odroid/edge: bump to 6.5.y from -rc6; rebase all patches vs v6.5(.0) View the full article

uefi-arm64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0); fix Phytium's stmmac patch uefi-arm64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0); fix Phytium's stmmac patch hammer patch driver-phytium-stmmac-acpi.patch use .remove_new due to "net: stmmac: Make stmmac_pltfr_remove() return void" View the full article

meson64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0) meson64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0) drop upstreamed patch meson-dts-add-missing-cache-properties.patch View the full article

bcm2711/edge: bump to RPi Foundation's 6.5.y branch; rebase all patches bcm2711/edge: bump to RPi Foundation's 6.5.y branch; rebase all patches View the full article

Description Update odroidxu4-current kernel to 5.4.255. 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 [ ] 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 the HiKey 960 board. How Has This Been Tested? [x] Boot from SD Card [x] Serial console [x] USB ethernet [x] WLAN 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