RSS Bot

Description As per title and move RK3588 EDGE tag to 6.6.y branch enable EDGE on Khadas Edge 2 Jira reference number AR-1913 How Has This Been Tested? [x] Build test 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

Description On images with changed vendor, when update comes from Armbian repository, VENDOR is overwritten. This change keeps the VENDOR variable from image. How Has This Been Tested? [x] Manual run 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] 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 Converting #5898 to use hook instead of patch 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] U-boot compiles. Also .config shows 648 as the default dram clk value. 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 For lichee-pi 4A has pwm-fan node in devicetree such as: fan: pwm-fan { compatible = "pwm-fan"; #cooling-cells = <2>; pwms = <&pwm 1 10000000 0>; cooling-levels = <0 64 192 255>; }; So enable pwm-fan support default with licheepi-4a. And I test it's worked on my licheepi 4a board with 8GB ddr. 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] Test on licheepi 4A board with 8GB ddr 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 Better labeling system and clear instructions should improve chaos in PR / issues. Adding label table. To do: add clear instructions how to use them implement https://github.com/lannonbr/issue-label-manager-action (doesn't work reliably, need to fix it) View the full article

Description NanoPC-T6 was added to mainline so is now already present in the Collabora kernel: remove our copy of the device tree Update tags to use newest (6.7-rc) How Has This Been Tested? Build checked. 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

initrd: cache: add /etc/modprobe.d to cache key (eg for MODULES_BLACKLIST) initrd: cache: add /etc/modprobe.d to cache key (eg for MODULES_BLACKLIST) View the full article

Description A lot of people has been asking on the forums for host mode not working on the otg port in 6.1+ kernel. It seems to be caused by patches.megous/usb-musb-sunxi-Avoid-enabling-host-side-code-on-SoCs-where-it-s.patch. The patch claims to solve sleep issue (rtcwake not working) on pinephone. As we don't support pinephone, I don't see any issue disabling 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] Tested host mode works on otg port on Orange Pi Zero (H3) and NanoPi Duo2 (H3) [X] Tested rtcwake continues to work on NanoPi Duo2 (H3), Orange Pi Prime (H5) and Orange Pi 3 LTS (H6) 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 title + attach sources to commit ID How Has This Been Tested? [ ] Build test 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 Bug fixes for Action scripts. View the full article

Description There are many changes in this file and its impossible to cover this with a patch for now current and all kernels back We are using same hack in UWE drivers. This fixes compilation breaking for kernel 6.7.y How Has This Been Tested? [x] Patch test [ ] Build test View the full article

Description This is a follow-up of: https://github.com/armbian/build/pull/5901 It resolves a conflict between the SimpleDRM and Panfrost graphic drivers by blacklisting simpledrm. Other boards of the same family are assumed to have the same issue and will probably benefit from this fix as well. However, the fix has been actually tested only on the Khadas VIM3. I cannot test this change for other boards, as I do not own them. The Banana Pi M5 was also included for this change, because the driver conflict has also been mentioned in another Jira ticket. Note that this board is of the meson-sm1 family! How Has This Been Tested? Perhaps someone else has these boards available for testing? 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 [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article

Bumps tspascoal/get-user-teams-membership from 2 to 3. Release notes Sourced from tspascoal/get-user-teams-membership's releases. 3.0.0 What's Changed Upgrade action node runtime to version 20 by @​tspascoal in tspascoal/get-user-teams-membership#21 Full Changelog: https://github.com/tspascoal/get-user-teams-membership/compare/v2...v3.0.0 v2.1.0 What's Changed Features feat: update checking functionality to support checking if user exists in one of multiple teams by @​binayabaral in tspascoal/get-user-teams-membership#17 Dependency Updates Bump @​actions/core from 1.10.0 to 1.10.1 by @​dependabot in tspascoal/get-user-teams-membership#18 Bump @​vercel/ncc from 0.36.1 to 0.38.0 by @​dependabot in tspascoal/get-user-teams-membership#19 New Contributors @​binayabaral made their first contribution in tspascoal/get-user-teams-membership#17 Full Changelog: https://github.com/tspascoal/get-user-teams-membership/compare/v2...v2.1.0 Commits 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 working：WiFi，HDMI，SATA，ETH not work：digital display，IR... 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 These are dead kernels with no ties to either vendor or mainline support. Remove patchsets to reduce clutter and confusion for any/all future contribution. (Example: Fixes should be posted to all LTS and current stable mainline kernel, not to these dead ones) How Has This Been Tested? Kernels have to be manually selected be editing config files, they aren't being used in the build system itself, any niche use for them can be accomplished by pulling them from history by the user. 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 RTL8153B - does not initialize correctly on boot. Reboot is okay. Start delay work-around in the board file needs tweaking for longer boot time. Jira reference number AR-1910 How Has This Been Tested? [x] Kernel 6.1y tested on Orange Pi R1 Plus LTS [x] Kernel 6.6y tested on Orange Pi R1 Plus LTS 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 Some high-resolution monitors (QHD/4K) will not output the desktop, and will enter sleep mode, directly after booting up an Armbian 23.8.1 desktop image and completing the initial setup questions. When such a monitor is attached, the kernel will auto-detect the SimpleDRM graphics driver, which is then prioritized over the Panfrost graphics driver. However, SimpleDRM outputs to a virtual output, while Panfrost outputs to the actual HDMI port. This causes the monitor to not receive any data. By blacklisting the simpledrm kernel module, Panfrost will take care of accelerated graphics (for any monitor) by default. Advanced users can still access simpledrm if required. Jira reference number [AR-1908] How Has This Been Tested? An Armbian image with a Cinnamon desktop has been build using the default options. That image has been written to a SD-card and tested on both a QHD monitor (that had the initial problem) and an older Full HD monitor (that worked fine before as well). In both test cases, the simpledrm kernel module was not loaded. The desktop was visible on the HDMI output both on initial boot and after subsequent reboots. 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 [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article

rk3588: experimental UEFI edk2 support core extensions: fix: don't redefine extension_function_info when recursing otherwise when there's a chain of enable_extension() we lose the original info extensions: grub-with-dtb: add UMS menu entry to GRUB if initramfs ums hook is detected this allows user to enter UMS mode from GRUB for usage with the initramfs-usb-gadget-ums extension has no effect unless initramfs-usb-gadget-ums extension is enabled together with grub-with-dtb extensions: initramfs-usb-gadget-ums: kernel cmdline enables initramfs UMS of all block devices this optional extension adds an initramfs script that: enumerates and filters all block devices exposes each device as an UMS (USB Mass Storage) in an USB Gadget loops forever with info (board never boots) the idea here is to compensate for UEFI's lack of "ums" or "rockusb" mode that's present in u-boot it also allows to expose USB/NVMe devices that might or not be detected by bootloader, if the kernel works extensions: uefi-edk2-rk3588: deploy edk2 (not u-boot) for rk3588 boards this extension is 100% optional and shouldn't adversely affect any builds if not enabled requires UEFI_EDK2_BOARD_ID to be set in board file, so we know which UEFI/edk2 build to use it finds the latest edk2 version from GitHub automatically (currently v0.9.1) it downloads (and caches) the correct edk2 build image automatically if forces certain aspects of the image: must use GPT partitioning must NOT use a separate /boot partition it disables the building and deploying of u-boot completely (thus blobs etc are from edk2) it creates a GPT "uboot" partition pointing to edk2's FIT, required by SPL this extension: automatically enables 'grub-with-dtb' automatically enable 'initramfs-usb-gadget-ums', to compensate for lack of ums/rockusb since we dont have u-boot anymore rk3588: configure UEFI_EDK2_BOARD_ID for all UEFI-supported boards From https://github.com/edk2-porting/edk2-rk3588/releases/tag/v0.9.1 For example, for rock-5b_UEFI_Release_v0.9.1.img UEFI_EDK2_BOARD_ID is rock-5b Important: this has no effect unless optional extension is enabled to test this out: make sure to read carefully the instructions at https://github.com/edk2-porting/edk2-rk3588/blob/master/README.md suppose you previously built the regular u-boot version with: ./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy now you can build the UEFI version with: ./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy EXT=uefi-edk2-rk3588 write the produced image to SD or eMMC and boot it use normally, or enter "UMS" mode by selecting that option in the grub menu You can write image to eMMC, boot it, enter UMS, write it again to NVMe, reboot, press in UEFI and boot from NVMe Also works if .img is written to eg USB stick, and UEFI edk2 is separately deployed to SPI flash Important: make absolutely sure you are able to force Maskrom mode (by shorting pins, pressing buttons, etc) before writing an UEFI image to eMMC; UEFI has no RockUSB ("Loader mode" support) at all. The new "initramfs-usb-gadget-ums" extension hopes to address this, but it is not guaranteed to work. View the full article

Description Adjusting text, remove broken coloring scheme View the full article

Description This tries to lower the DRAM frequency of Tritium H5 like what is done on other H5 boards, because I met stability issues when running Klipper on it. How Has This Been Tested? I built a U-Boot deb and flashed it to my Tritium H5, and the stability enhances. 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

No descriptionView the full article

To ensure the Linux kernel is running smoothly, it requires maintenance from a variety of levels. Those working on the lower levels, or the plumber layers, of the kernel will have a chance to convene next week at the annual Linux Plumbers Conference. View the full article

Description media: fix firefly-rk3399 mini-pcie slot. Problem description: The 3G/4G module is not available on the firefly-rk3399. According to the schematic, the "MINI PCIE" on the firefly-rk3399 only has USB2 functionality. Comparing with the official kernel device tree, it is found that the vcc3v3-3g-regulator power supply node is missing. However, the pins used by this node conflict with the leds node referenced in the kernel device tree for roc-rk3399-pc. This node is redundant in firefly-rk3399, so it is defined as "node deletion". Summary of modifications: Added vcc3v3-3g-regulator power supply node. Defined node deletion. How Has This Been Tested? [x] Successfully built. [x] System startup. [x] The USB2 functionality of "MINI PCIE". 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