RSS Bot

thinkpad-x13s: firmware PR has landed, remove usage of rogue fw fork thinkpad-x13s: firmware PR has landed, remove usage of rogue fw fork View the full article

Khadas VIM3/VIM3L u-boot 23.07-rc4 + SPI-NOR/MTD booting support (with old FIP blobs) khadas-vim3: bump u-boot to 2023.07-rc4, add KBI support for easy PCI/USB3 switching this introduces the v2023.07 u-boot patch directory, with the boot-usb-nvme-scsi-first patch rebased add myself as BOARD_MAINTAINER khadas-vim3: introduce SPI-NOR/MTD u-boot build, using old(er) FIP blobs move FIP signing code from meson-g12b.conf's uboot_custom_postprocess() to the board's own post_uboot_custom_postprocess hook fetch a secondary FIP blob repo at a revision with working FIP blobs for SPI (see https://github.com/LibreELEC/amlogic-boot-fip/pull/10) implement post_uboot_custom_postprocess__khadas_vim3_uboot_new_and_old_blobs() doing a dance for SD/eMMC with new blobs, and SPI with old blobs. khadas-vim3l: bump u-boot to 2023.07-rc4, add KBI support for easy PCI/USB3 switching symlink in patch/u-boot/v2023.07 from board_khadas-vim3 to board_khadas-vim3l since KBI is the same for both add myself as BOARD_MAINTAINER khadas-vim3l: introduce SPI-NOR/MTD u-boot build, using old(er) FIP blobs move FIP signing code from meson-sm1.conf's uboot_custom_postprocess() to the board's own post_uboot_custom_postprocess hook fetch a secondary FIP blob repo at a revision with working FIP blobs for SPI (see https://github.com/LibreELEC/amlogic-boot-fip/pull/10) implement post_uboot_custom_postprocess__khadas_vim3l_uboot_new_and_old_blobs() doing a dance for SD/eMMC with new blobs, and SPI with old blobs. View the full article

meson64 general asound.state fix; Khadas VIM3/VIM3L asound.state fixes for HDMI audio meson-{sm1|g12a|g12b}: default, but don't override, ASOUND_STATE; this way board-specific asound.state's are honored add logging during actual deployment so we know what is happening khadas-vim3: update asound.state enabling HDMI out khadas-vim3l: update asound.state with correct card name and enable HDMI output View the full article

fixes #5381 allows building other git.kernel.org-hosted forks, e.g. KERNELSOURCE='https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git' 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

This brings the patch set up to 2023-06-22 wireless-next Drivers tested; 8822CS. 8821CU and 8723DS Notables; Not seeing random dmesg spam rtw_8822cs failed to get tx report from firmware which I would see on both the CS and CU from time to time. [ ] 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 sunxi-6.2 Small correction incorrect spelling 'fixses' directory files which don't apply when checking series.armbian How Has This Been Tested? Patches apply finding correct directories after changes [ ] Test A [ ] Test B 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

cleanup-space-final-image: keep qcom and qed firmware (for thinkpad-x13s) cleanup-space-final-image: keep qcom and qed firmware (for thinkpad-x13s) View the full article

armbian-kernel: further insist on disabling kernel debug, since DEBUG_INFO is auto-enabled by DEBUG_INFO_DWARF5 and others armbian-kernel: further insist on disabling kernel debug, since DEBUG_INFO is auto-enabled by DEBUG_INFO_DWARF5 and others View the full article

thinkpad-x13s: add wip board; use steev's 6.3.y kernel as an uefi-arm64 BRANCH=sc8280xp; force modules & fw in initrd thinkpad-x13s: add wip board; use steev's 6.3.y kernel as an uefi-arm64 BRANCH=sc8280xp; force modules & fw in initrd add GRUB_CMDLINE_LINUX_DEFAULT with efi=noruntime clk_ignore_unused pd_ignore_unused so it actually boots use grub-with-dtb for the (required) DTB usage in grub use a customize hook to add a lot of modules & fw into initrd, required for booting if on RELEASE=lunar, add Ubuntu's "x13s Concept" PPA and a few packages for battery control/audio View the full article

grub: add hooks, fix GRUB font & wallpaper, introduce grub-with-dtb extension grub: add hooks, fix GRUB font & wallpaper, introduce grub-with-dtb extension introduce hooks grub_early_config, grub_pre_install and grub_late_config what we see here is an extension that itself has hooks, that just works introduce extension grub-with-dtb, which enables grub extension requires BOOT_FDT_FILE to be set includes /etc/armbian-grub-with-dtb with BOOT_FDT_FILE= in the bsp-cli includes /etc/kernel/postinst.d/armbian-grub-with-dtb in the bsp-cli which reads the above and creates links for /boot/armbian-dtb-<version> when deploying deb's adds implementations of the hooks above to replace the distro's 10_linux with our own 09_linux_with_dtb which looks for /boot/armbian-dtb-<version> forcibly run /etc/kernel/postinst.d/armbian-grub-with-dtb during image build, since bsp-cli is installed after linux-image uefi-arm64: enable GRUB wallpaper by setting UEFI_GRUB_TERMINAL=gfxterm force GRUB_FONT so Ubuntu is not confused and gfxterm (incl wallpaper) finally works View the full article

Description Bump U-boot to 2023.01. Backported dts patch from 2023.07-rc4 to fix compilation of bigtreetech-cb1 board. Jira reference number AR-1753 How Has This Been Tested? [X] Built images for all of the Maintained and community supported allwinner boards [X] Booted on Nanopiduo2 and checked that crust continues to work 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 This reverts commit a41e768f53c522259f373f84f0455c66b06031b2 This code needs to be properly reviewed ... can take a week or a year. Project have no plans to redirect resources to support desktop development. Opening, closing, new PR, closing, attention, opening, attention, closing, ... What a waste of resources. And abuse - seeking for attention and waiting that someone breaks and approves the code that we never planned, have no urgency label, is not ready and was probably not even tested. It just looks less crazy as the one with 2000 files. This is why I am reverting the code in first place. Second is that we need to strive to be better in doing this and always making a better code. If proposed is obviously worse then what we have now, its rejected without any debate. There is not much difference between Bookworm and Bullseye that it would justify such a big code change. Every line of PR code needs to have a justification as every line of code is a liability. I have no interest to apply additional rework once again: https://github.com/armbian/build/commit/e71d8dba103893e662e60fdf675b90ca78529888 https://github.com/armbian/build/commit/ce68e373f1a9f664a65dd96f9ddc7714e243d491 https://github.com/armbian/build/commit/74aa5d9e0a23b949df7ff0c2bcda6666897c20b9 No fu* way. View the full article

Add gnome desktop to bookworm builds View the full article

Adding the mate desktop to bookworm builds View the full article

New Bookworm Desktops XFCE : Removed skel and moved to xdg. added debian dir with xdg-xfce dir with files need for configuring desktop Re-Aranged the appgoup folder per debian to put apps in correct groups and more proficient naming scheme moved printing and filesharing to appgroups. New theme to desktop. xdg changes are based on : https://forum.xfce.org/viewtopic.php?id=13308 #3 Rebuilt for bookwork following Debain Guidelines 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 As per title How Has This Been Tested? [x] Build test Checklist: [x] My code follows the style guidelines of this project [x] My changes generate no new warnings View the full article

Taking place at the Prague Congress Centre from June 27 to 30, this new 4-day umbrella event brings multiple conferences, including Automotive Linux Summit (ALS) and Embedded Linux Conference (ELC), all under one roof. View the full article

Adding in support for new desktop being added . i3 lxde lxqt and others to be added as made View the full article

Fix path for img in the lightdm login background View the full article

Description Instead of requesting to install gcc-or1k-bin package unconditionally, request it only when building images with crust support. Also consolidated crust related configuration into a separate file. Jira reference number AR-1786 How Has This Been Tested? [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopineo works as it doesn't need crust support [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopiduo2 fails as it bullseye doesn't include gcc-or1k-bin package and hence reported as unsupported system [X] ./compile.sh BOARD=nanopiduo2 works as default release is jammy that has the required package 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 I just move config/kernel/linux-rockchip-rk3588-legacy.config to config/kernel/linux-rk35xx-legacy.config, and make them share the same family rk35xx. Now rk356x will use the same kernel rk3588 legacy is using. I tested the new kernel on my rock3a, working well. 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 legacy kernel of rock3a and rock5b, same result. [x] New kernel works on rock3a. 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 ports over recent changes for the Orange Pi Zero 2 board brought by AGM1968 for 6.2.y kernel, back to 6.1.y kernel (current LTS). Changes being ported (minor modifications required to the patching metadata, overall code & structure intact): https://github.com/armbian/build/pull/5247 (CPU scaling) https://github.com/armbian/build/pull/5270 (on-board LED states changes) How Has This Been Tested? CPU scaling tests [x] Test A: Build & boot-up the board, making sure it still works [x] Test B: Run ThomasKaiser/sbc-bench See: https://github.com/mdziekon/armbian-build/pull/2 LED changes tests [x] Test A: Build & boot-up the board, making sure it still works, and the LED changes have been applied 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

Powered by Rust, the video codec stack on ARCVM is now bringing faster and more reliable video decoding on ChromeOS. Here's how Collabora has been helping shape video virtualization for Chromebooks, and what it means for end users. View the full article

Update maintainers synched from the database View the full article

All patches apply and resolves issue: https://github.com/armbian/build/issues/5357 Jira reference number AR-1785 [ ] 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