RSS Bot

Description Necessary changes only to make repository work. There is probably lots of work to do laser... Jira reference number [AR-9999] How Has This Been Tested? Builds until the point where it tries to grab release file form apt repo which obviously fails. 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 Converted configuration for uwe5622 support to extension making it easier to add wifi and bluetooth support to boards with uwe5622 wireless module. Added the uwe5622 extension to Orange Pi Zero2. This should add bluetooth support to the same. Moved Orange Pi 3 LTS specific code out of the family config file Also for H6 based devices, switched to lightdm-gtk-greeter as slick-greeter shows weird artifacts Also added myself as maintainer for Orange Pi 3 and Orange Pi 3 LTS. 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 wifi, bluetooth and login screen on Orange Pi 3 LTS 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 The lm75 sensor was defined in the dts as "onnn,lm75". Set it to "national,lm75" as is set in the upstream dts. (there is no such thing as "onnn,lm75"). Later on (or maybe I should include it there) we should remove the lm75 module from MODULES and MODULES8lEGACY in config/boards/helios64.csc, as the DTS already loads it. (which makes me think "onnn,lm75" as a DTS node never was recognized by a kernel, thus the need to explicitly load lm75). How Has This Been Tested? [x] remove lm57 from the config (I believe it was /etc/modules but is long gone) and reboot with new dts 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 Fix compilation warnings [🐳|🔨] CC arch/arm/mach-rockchip/boot_mode.o (...) [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c: In function ‘rockchip_dnl_mode_check’: [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:174:24: warning: ‘return’ with a value, in function returning void [-Wreturn-type] [🐳|🔨] 174 | return 0; [🐳|🔨] | ^ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:166:6: note: declared here [🐳|🔨] 166 | void rockchip_dnl_mode_check(void) [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:183:24: warning: ‘return’ with a value, in function returning void [-Wreturn-type] [🐳|🔨] 183 | return 0; [🐳|🔨] | ^ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:166:6: note: declared here [🐳|🔨] 166 | void rockchip_dnl_mode_check(void) [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:196:17: warning: implicit declaration of function ‘cli_simple_run_command’ [-Wimplicit-function-declaration] [🐳|🔨] 196 | cli_simple_run_command(cmd, 0); [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:170:13: warning: unused variable ‘ret’ [-Wunused-variable] [🐳|🔨] 170 | int ret = 0; [🐳|🔨] | ^~~ it could be that adding the missing cli include fix functionality. So this patch might be more than cosmetic. 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 u-boot for helios64 board (v2022.07) and boot with this u-boot. -./compile.sh uboot BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no ARTIFACT_IGNORE_CACHE="yes" The CONFIG_SYS_SCSI_MAX_DEVICE definition removal from u-boot v2022.04 (as since this version this is a macro) I have only build tested with: ./compile.sh uboot BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no ARTIFACT_IGNORE_CACHE="yes" BOOTBRANCH="tag:v2022.04" BOOTPATCHDIR="u-boot-rockchip64-v2022.04" 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

As 2023 draws to a close, I wanted to give a quick update on NVK, what's happened this year, and where we'll be headed in 2024. While previous posts have focused primarily on the technical details, this post will be more geared towards users. View the full article

Description Switch back to Rockchip DDR binary for DDR initialization in u-boot for Helios64. I believe there is nothing board-specific about this memory initialization issue, but it might be no other Armbian board has this combination of rk3399 and LPDDR4. Else there is something specific about the memory set up on the Helios64 hardware. On the Helios64 random memory errors happens when using the U-Boot DDR intialization code for rk3399. Switching to the rkbin rk33 933MHz v1.25 allows this testcase to run more than once without a memory error: for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done Could be LPDDR4 specific. Workaround https://github.com/armbian/build/issues/4761 "free() invalid pointer". A proper fix would be to fix u-boot own lpddr4 initialization code for Rockchip but I miss the Rockchip DDR binary settings to compare with. 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 ] run for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done multiple times 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

Google Open Source have chosen their second group of winners for the 2023 Google Open Source Peer Bonus Program, and Arnaud Ferraris, Senior Software Engineer at Collabora and Mobian project lead, is among the recipients! View the full article

Description It breaks EDGE compilation as define was done only for legacy. How Has This Been Tested? Manual build. View the full article

Bumps github/codeql-action from 2 to 3. Release notes Sourced from github/codeql-action's releases. CodeQL Bundle v2.15.4 Bundles CodeQL CLI v2.15.4 (changelog, release) Includes the following CodeQL language packs from github/codeql@codeql-cli/v2.15.4: codeql/cpp-queries (changelog, source) codeql/cpp-all (changelog, source) codeql/csharp-queries (changelog, source) codeql/csharp-all (changelog, source) codeql/go-queries (changelog, source) codeql/go-all (changelog, source) codeql/java-queries (changelog, source) codeql/java-all (changelog, source) codeql/javascript-queries (changelog, source) codeql/javascript-all (changelog, source) codeql/python-queries (changelog, source) codeql/python-all (changelog, source) codeql/ruby-queries (changelog, source) codeql/ruby-all (changelog, source) codeql/swift-queries (changelog, source) codeql/swift-all (changelog, source) CodeQL Bundle Bundles CodeQL CLI v2.15.3 (changelog, release) Includes the following CodeQL language packs from github/codeql@codeql-cli/v2.15.3: codeql/cpp-queries (changelog, source) codeql/cpp-all (changelog, source) codeql/csharp-queries (changelog, source) codeql/csharp-all (changelog, source) codeql/go-queries (changelog, source) codeql/go-all (changelog, source) codeql/java-queries (changelog, source) codeql/java-all (changelog, source) codeql/javascript-queries (changelog, source) codeql/javascript-all (changelog, source) codeql/python-queries (changelog, source) codeql/python-all (changelog, source) codeql/ruby-queries (changelog, source) codeql/ruby-all (changelog, source) codeql/swift-queries (changelog, source) codeql/swift-all (changelog, source) CodeQL Bundle Bundles CodeQL CLI v2.15.2 (changelog, release) Includes the following CodeQL language packs from github/codeql@codeql-cli/v2.15.2: codeql/cpp-queries (changelog, source) ... (truncated) Changelog Sourced from github/codeql-action's changelog. Commits 3a9f6a8 update javascript files cc4fead update version in various hardcoded locations 183559c Merge branch 'main' into update-bundle/codeql-bundle-v2.15.4 5b52b36 reintroduce PR check that confirm action can be still be compiled on node16 5b19bef change to node20 for all actions f2d0c2e upgrade node type definitions d651fbc change to node20 for all actions 382a50a Merge pull request #2021 from github/mergeback/v2.22.9-to-main-c0d1daa7 458b422 Update checked-in dependencies 5e0f9db Update changelog and version after v2.22.9 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

Bumps actions/upload-artifact from 3.1.3 to 4.0.0. Release notes Sourced from actions/upload-artifact's releases. v4.0.0 What's Changed The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements. For more information, see the @​actions/artifact documentation. New Contributors @​vmjoseph made their first contribution in actions/upload-artifact#464 Full Changelog: https://github.com/actions/upload-artifact/compare/v3...v4.0.0 Commits c7d193f Merge pull request #466 from actions/v4-beta 13131bb licensed cache 4a6c273 Merge branch 'main' into v4-beta f391bb9 Merge pull request #465 from actions/robherley/v4-documentation 9653d03 Apply suggestions from code review 875b630 add limitations section ecb2146 add compression example 5e7604f trim some repeated info d6437d0 naming 1b56155 s/v4-beta/v4/g 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

There is no B model (yet). rpi4b has the b attached since it is FK__MACHINE_MODEL="Raspberry Pi 4 Model B" View the full article

Description Status maintenance tasks. Jira reference number AR-2000 How Has This Been Tested? n/a 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 This patch PCIE initialization error after warm reboot. Typical error log after warm reboot: [ 2.510082] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.510139] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.510160] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.510748] rockchip-pcie f8000000.pcie: no bus scan delay, default to 0 ms [ 2.510795] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 3.011274] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.011373] rockchip-pcie: probe of f8000000.pcie failed with error -110 The root of cause is when device is booted after power on PHY stay in "factory" state. After warm boot PHY stay in previous state and prevent any training and PCIE init fail. Log after fix PHY: [ 2.296993] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.297064] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.297100] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.298098] rockchip-pcie f8000000.pcie: no bus scan delay, default to 0 ms [ 2.298169] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.324717] rockchip-pcie f8000000.pcie: wait 0 ms (from device tree) before bus scan [ 2.325477] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00 [ 2.325499] pci_bus 0000:00: root bus resource [bus 00-1f] [ 2.325518] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff] [ 2.325537] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff]) How Has This Been Tested? [X] Tested on NanoPI R4S with current kernel - OK. [X] Tested on NanoPI R4S with edge kernel - OK. 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 WAN ethernet does not work on NanoPI R2C on edge because GMAC_CLK pin on PHY not provides output clock (for GMAC) by default. This updated device tree fix this issue. current and legacy branches have different (out of kernel) driver and don't need this dts fix. [ 2.902617] rk_gmac-dwmac ff540000.ethernet: IRQ eth_wake_irq not found [ 2.902640] rk_gmac-dwmac ff540000.ethernet: IRQ eth_lpi not found [ 2.902793] rk_gmac-dwmac ff540000.ethernet: PTP uses main clock [ 2.903026] rk_gmac-dwmac ff540000.ethernet: clock input or output? (input). <- this clock MUST be provided by PHY [ 2.903049] rk_gmac-dwmac ff540000.ethernet: TX delay(0x22). [ 2.903059] rk_gmac-dwmac ff540000.ethernet: RX delay(0x12). [ 2.903078] rk_gmac-dwmac ff540000.ethernet: integrated PHY? (no). [ 2.903136] rk_gmac-dwmac ff540000.ethernet: clock input from PHY [ 2.908159] rk_gmac-dwmac ff540000.ethernet: init for RGMII [ 2.910080] rk_gmac-dwmac ff540000.ethernet: User ID: 0x10, Synopsys ID: 0x35 [ 2.910108] rk_gmac-dwmac ff540000.ethernet: DWMAC1000 [ 2.910116] rk_gmac-dwmac ff540000.ethernet: DMA HW capability register supported [ 2.910123] rk_gmac-dwmac ff540000.ethernet: RX Checksum Offload Engine supported [ 2.910129] rk_gmac-dwmac ff540000.ethernet: COE Type 2 [ 2.910135] rk_gmac-dwmac ff540000.ethernet: TX Checksum insertion supported [ 2.910141] rk_gmac-dwmac ff540000.ethernet: Wake-Up On Lan supported [ 2.910236] rk_gmac-dwmac ff540000.ethernet: Normal descriptors [ 2.910245] rk_gmac-dwmac ff540000.ethernet: Ring mode enabled [ 2.910252] rk_gmac-dwmac ff540000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 22.330038] rk_gmac-dwmac ff540000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 22.340509] rk_gmac-dwmac ff540000.ethernet eth0: PHY [stmmac-0:03] driver [YT8521 Gigabit Ethernet] (irq=POLL) [ 22.348004] rk_gmac-dwmac ff540000.ethernet eth0: No Safety Features support found [ 22.348040] rk_gmac-dwmac ff540000.ethernet eth0: PTP not supported by HW [ 22.351173] rk_gmac-dwmac ff540000.ethernet eth0: configuring for phy/rgmii link mode How Has This Been Tested? [X] Build patched image and test on target 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Reapply https://github.com/armbian/build/commit/305886b111ff76a53693a3c171751a8830d106c5 and fix compilation & spi image booting 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 and boot 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 Not sure if this PR makes any sense but welp. I leave that to those who actually know what they are doing ^^ Anyway just for the heck of it I tried what happens if I build Station-P1 against rockchip64 family instead of media Jira reference number [AR-x] How Has This Been Tested? [x] Build Bookworm CLI edge with Linux 6.6.7 [x] Boot Bookworm CLI works [x] Enable 2GHz OC overlay works [x] Install to eMMC works [x] Desktop XFCE works [ ] WiFI does not work but might have been broken before as well. No clue. armbianmonitor: https://paste.armbian.com/oyoyiqoper 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 uboot 'button' cmd and add Recovery button to rk3318 uboot dts. In the linux kernel dts button is labeled lowercase "recovery", but I've chosen "Recovery" as it is more frequent in uboot dts'es: $ (cd cache/sources/u-boot-worktree/u-boot/v2022.07/arch/arm/dts; grep -ir 'label.*"recovery"' .) ./rk3399-nanopc-t4.dts: label = "Recovery"; ./rk3399-khadas-edge.dtsi: label = "Recovery"; ./rk3399-roc-pc.dtsi: label = "Recovery"; ./rk3328-rock-pi-e.dts: label = "Recovery"; ./rk3066a-mk808.dts: label = "recovery"; ./rk3399-nanopi-m4b.dts: label = "Recovery"; How Has This Been Tested? [x] boot rk3318 with modified uboot.cmd to test new command: if button Recovery; then echo "Recovery ON" else echo "Recovery OFF" fi 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 Add patches to support HEVC hardware video decoder provided by rkvdec in rockchip64 socs like rk3328 and rk3399. This leverages the hardware features reducing cpu usage by a wide margin. Also provides some patches and fixes for v4l2 whose patch files seems big, but most is just description text. Can be tested along with the repository published by me on this forum post. Jira reference number AR-1997 How Has This Been Tested? [x] Compile current 6.1 rockchip64 kernel [x] Compile edge 6.6 rockchip64-kernel [x] Test current kernel on existing rk3399 installation on OrangePi4 LTS board [x] Test edge kernel on existing rk3399 installation on OrangePi4 LTS board No harmful side effects have been detected during tests, the system seems stable. Test against 1080p60 h.264 video: Test against 1920x860p30 h.265 video: 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 Related to auto-test system only. View the full article

Description We are storing logs at our pastebin server(s). Switching back to primary as secondary is failing. paste.next.armbian.com -> paste.armbian.com How Has This Been Tested? Made one test build with SHARE_LOG=yes which generated logs on paste bin server. 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 View the full article

Description As per subject, plus kernel configs have been updated and enabled rtl8xxx untested wifi chips How Has This Been Tested? [x] Kernel patches apply with current kernel [x] Kernel patches apply 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 [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, plus kernel configs have been updated and enabled rtl8xxx untested wifi chips How Has This Been Tested? [x] Kernel patches apply with current kernel [x] Kernel patches apply 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 [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

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 Clean deprecated parts in patches. How Has This Been Tested? [x] Build test 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