RSS Bot

Remark: This PR is based off v23.11 for now and will be rebased of main/master branch before review Description Running "uefi-x86" board image on qemu-system-x86_64 --display none --serial stdio ... did not: allow GRUB boot without GUI display display early kernel boot messages on the serial console display the console prompt on serial console Jira reference number: None 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: Boot uefi-x86 board image on qemu-system-x86_64 --display none --serial stdio ... [ ] Test B: Boot uefi-x86 board image on qemu-system-x86_64 --display vga 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

Now included in our Debian images & available via our GitLab, you can build a complete, working BL31 (Boot Loader stage 3.1), and replace the closed binary blob with an open-source binary that anyone can compile. View the full article

Description ddbr was failing on a recent jammy build. The issue is that lsblk output has changed sometime since this script was written. The logic to parse out the $runfrom drive was returning duplicate info, so instead of 'mmcblk0' the value was 'mmcblk0 mmcblk0' Having this duplicate value was causing an error further down the script. Fix is to add ' | sort | uniq' this was already being done on the other lsblk outputs, just not this one. I've run into this before, and I guess at that time, I forgot to submit a PR for the fix, or it was for a different script that had the same issue. Changes to be committed: modified: packages/bsp/common/usr/sbin/ddbr 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] Tested backup on board that was failing without this fix Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description The kernel headers package is not getting installed due to missing common_drivers/header_include.mk file. Jira reference number AR-2072 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 installing kernel headers on vim1s 24.02 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

Description The user idubrov reported on forums and discord that the current and edge images are not bootable from sdcard as mmc driver fails to probe due to regulator not being available. This is a regression that happened due to switching from bigtreetech provided axp313a driver to mainline axp313a driver. Updating regulator node name in dts apparently makes it work with the upstream driver as tested by the user. I have also noticed that CI was not covering current and edge kernel for this board. I have enabled the same to make sure we will be aware of such issues in the future. 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 only that patches apply correctly as I don't really have the board. 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

Changes to be committed: modified: config/boards/aml-s9xx-box.tvb deleted: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf new file: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template Description Upgrades of the aml-s9xx-box bsp package were failing (apparently I've never tested this, nor has anyone reported it) The problem is that the package installs files into /boot which is a fat filesystem. dpkg doesn't support the fat filesystem for upgrades as it tries to create a backup link for each file it is replacing which fails. Solution is to remove the files being replaced in a preinst step This also necessitated using the standard armbian extlinux.conf file as installing a custom one would result in the extlinux.conf file being replaced (without the append line being added, thus making the box unbootable after upgrade) 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] Tested new image works [x] Tested upgrading and reinstalling the armbian-bsp-cli-aml-s9xx-box-current deb 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 View the full article

Back in 2022, after a series of issues were found in its design, I made the call to rework some of WirePlumber's fundamentals in order to allow it to grow. So where are we we now? And what's next? Let's dive in! View the full article

Changes to be committed: modified: VERSION Description It bugs me that nightlies are at 24.5 but main is still at 24.2 Jira reference number [AR-9999] Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description When booting from UHS-I cards on VIM4 and VIM1S, mine was Samsung EVO Plus card (MB-MC64KA), booting only worked 1 out of 5 reboots. Other times the device either tried booting from EMMC or from SPI flash. The following logs appear when booting doesn't work from sdcard mmc0 is current device sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** Using git bisect brought me to bfa451f commit and reverting the same solves the issue. Booting now works reliably from SD card every time I restart the same. Jira reference number AR-2070 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 rebooting multiple times when booting from sdcard on VIM4 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 Enable uboot gpio command. This would allow to set up rk3318-box'es LED display in custom uboot script. For example, to show "boot", this snippet can be added (gpio pins and letter codes should be adjusted for different STB/LCD models): FD650_MODE_WRCMD='0 1 0 0 1 0 0 0' DISPON='0 0 0 0 0 0 0 1' FD655_BASE_ADDR='0 1 1 0 0 1 1 0' Z='0 0 0 0 0 0 0 0' B='0 1 1 0 0 1 1 1' O='0 1 1 0 0 0 1 1' T='0 1 0 0 0 1 1 1' setenv d0 gpio clear C22 setenv d1 gpio set C22 setenv LC gpio clear C19 setenv HC gpio set C19 setenv send 'run d0 LC; for b in $cmd; do run d$b HC LC; done; run HC d1' cmd="$FD650_MODE_WRCMD 1 $DISPON 1" run send cmd="$FD655_BASE_ADDR 1 $Z 1 $B 1 $O 1 $O 1 $T 1" run send 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 and boot rk3318-box 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

mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot those patches are a mess, hopefully I'll find time to squash soon mekotronics 3588: squash u-boot patches same as before but not touching the same file twice+ View the full article

artifact-uboot: include BOOTCONFIG in u-boot artifact version hash artifact-uboot: include BOOTCONFIG in u-boot artifact version hash HOW did we get this far without this? should cause rebuild of all u-boots, hopefully View the full article

Collabora's engineers presented six talks over the course of the weekend, with topics including a review of recent improvements to GStreamer, a look at the state of video offloading on the Linux desktop, and more. View the full article

Build the Kernel DRDB as a module in linux-mvebu-config current and edge. close #6268 View the full article

Description Bump the K2 to u-boot 2024.01, let's try to get old u-boots out of our hair. How Has This Been Tested? builds and boots, everything works. 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 patch fixes the high interrupt issue on the Orange Pi5 Plus. Forum discussion available here. https://forum.armbian.com/topic/33360-orangepi-5-plus-rtc-hym8563-irq-issue/ The patch also adds poweroff support. Right now the Orange Pi 5 Plus just reboots when poweroff or shutdown -h now is executed. Third fix of the patch is to correct gpio_pwrctrl1 typo. 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 command ./compile.sh BOARD=orangepi5-plus BRANCH=edge RELEASE=trixie KERNEL_CONFIGURE=no BUILD_MINIMAL=yes BUILD_DESKTOP=no COMPRESS_OUTPUTIMAGE=img BOOTSIZE=512 [x] Booted the image and went through the first-run wizard [x] Checked the system via top and procinfo and monitored the cpu usage and interrupts 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 adds support for the Texas Instruments SK-AM68 and SK-AM69 boards. Notable features of SK-AM68 board: 16GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 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 One M.2 key M connector Notable features of SK-AM69 board: 32GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 4K resolution with MST support and HDMI Three CSI-2 ports compatible with Raspberry Pi 32 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 One M.2 key E connector and one M.2 key M connector Further details like features, schematics and purchase links can be found on the board page: SK-AM68 SK-AM69 Note: To support SK-AM69 board, we had to switch U-Boot source for K3 family devices to ti-u-boot:2023.04 (commit 1), since boot configs for SK-AM69 board has not been upstreamed yet. How Has This Been Tested? First, we verified that the changes introduced do not deprecate any existing board support by: [ ] Build and boot SK-AM62B Jammy CLI/Standard on Edge(v6.6) kernel [ ] Build and boot SK-AM64B Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-TDA4VM Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels Further, the functionalities of new boards were tested by: [ ] Build and boot SK-AM68 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-AM69 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Gbit Ethernet works [ ] USB 3.0 ports work 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

Engineers have widely adopted GStreamer to build video analytics pipelines, and while many companies have indeed built their machine learning analysis framework around GStreamer, no one had made the effort to contribute upstream, until now. View the full article

Description Z96a is a cloud laptop designed by Sunniwell.co from China, using rk3568b2 chip, 4g memory, 32g emmc, 1080p screen. Because of the manufacturer's special design, such as power chip rk817 etc.. drivers needs to be patched, so a new board family needs to be created. After creating a new board family, Added code will not affect the armbian historical or other boards. 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 A: Image which compiled by new code has been flashed in z96a, and everything works fine. 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 The idea is to generate output/git_sources.json file that will contain url, branch and commit hash combo. The easiest way to generate file for all devices is to run ./compile.sh targets. Then at the time of release we will copy the output/git_sources.json file to config/sources/git_sources.json. Once the file is copied, the hash information from the file will be used to fetch resources for git repositories where branches are specified instead of tags or commits. There can be other ways to do this as well. I am just too tired to experiment more on the same. Raising it to be a communication starter. I have also added the json file that I have generated today. I think it can be used to freeze sources for 24.02 release. Hence I have raised this PR again v24.02 branch 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. [ ] Tested output/git_sources.json file generation using ./compile.sh targets command [ ] Copied generated file to config/sources and modified it to use a different commit hash for 6.6 kernel. Then tested that kernel is being built from that hash instead of the latest available 6.6 kernel. 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

Patch for #6268 View the full article

Description Refresh kernel config to match fenix 1.6.4. This enables CONFIG_W1_SLAVE_THERM which was enabled on fenix as well. On bookworm, and also possibly on newer version of ubuntu, systemd starts all of the services present on first boot. Making the /etc/machine-id file empty ensures that machine id is still initialized on first-boot, while other services are not started automatically. This also seems to be observed by alex3d as well as reported in #6264 . However I was not able to reproduce the same issue on any of the other boards I have. Hence I have currently only handled it for meson-s4t7 family. This also makes the previous hack of masking chrony-wait.service unnecessary and hence I have reverted that change. 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 bookworm xfce image on vim1s. Lightdm no longer pops up before first login setup and also first login doesn't starts immediately as chrony-wait service is no longer started. 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

Continuing our Kernel Integration series, we're excited to introduce DRM-CI, a groundbreaking solution that enables developers to test their graphics subsystem patches across numerous devices within the community's shared infrastructure. View the full article

Description This commit re-applies previously utilized 'HACK' patches aimed at addressing eMMC phase clock configuration issues exclusively on JetHub D1, D1+, and H1 devices. No impact on other devices. Jira reference number AR-2049 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] D1+/H1 boots 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

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-2050 How Has This Been Tested? Boots current and edge kernel from SDcard images Built-in WiFi works in both cases However, board will not allow clocking >1.0Ghz Built-in WiFi antenna is very weak Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ x ] Generate current image [ x ] Generate edge image 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