RSS Bot

u-boot-menu: curb logging, no need to emit warn's here u-boot-menu: curb logging, no need to emit warn's here View the full article

Description Those are just small left over fixes for AR-1444 How Has This Been Tested? [ ] Manual repo generation Checklist: [ ] My changes generate no new warnings View the full article

Collabora's main testing laboratory has grown to automate testing on over 150 devices of about 30 different types. The lab receives job submissions from several CI systems, e.g. KernelCI, MesaCI, and Apertis QA. 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 Hello! Here is a patch that will add the device tree and defconfig for the NanoPC T6 in U-Boot, with support for booting from an NVMe SSD. Works excellent with https://github.com/armbian/linux-rockchip/pull/78. How Has This Been Tested? Note: My T6 did not come with a spi nor chip, so I soldered it myself. [x] Flashed the bootloader to the spi nor. [x] Booting from NVMe works as expected with the bootloader in the spi nor. 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 Update odroidxu4-current kernel to 5.4.252. 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

Rust is a modern language known for its memory safety, efficiency, and wide range of high-level features. But many beginners also run into something else in Rust: how surprisingly difficult it is to represent some common designs. View the full article

Description We package kernel debs with package name like linux-image-legacy-rk35xx. In general people treat legacy-rk35xx as the flavor. Debian's live-build will use it to generate grub config: https://salsa.debian.org/live-team/live-build/-/blob/master/scripts/build/binary_grub_cfg#L117. And ubiquity which is ubuntu's desktop installer also looks for it. So it's better to change our kernel filename to standard like vmlinuz-*${flavor}. 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 success for rk35xx legacy kernel [x] Kenel boots on rock5b 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

khadas-vim4/khadas-vim1s: very early wip; meson-s4t7/legacy 5.4 Amlogic kernel initrd: fix undeclared variable update_initramfs_cmd u-boot-menu: allow skipping U_BOOT_FDT even with BOOT_FDT_FILE set, by specifying EXTLINUX_SPECIFIC_FDT=no khadas-vim4/khadas-vim1s: very early wip; meson-s4t7/legacy 5.4 Amlogic kernel only "boot from SD" supported right now building uboot with xPack riscv-none-embed-gcc external toolchain setup in hooks kvim4: very high kernel logging + systemd debug logging to console kvim4/kvim1s: add uEnv.txt and ROOT_FS_LABEL="ROOTFS" and Khadas-esque extlinux meson-s4t7: unify khadas-vim1s and khadas-vim4 u-boot building kernel .config: s4t7: original Khadas vendor config s4t7: CONFIG_BINFMT_MISC=y s4t7: make NFS/sunrpc stuff =y s4t7: enable USB wifi drivers from Armbian network_drivers firmware: at https://github.com/armbian/firmware/pull/56 extlinux tricks require https://github.com/armbian/build/pull/5462 status: kvim1s: boots from SD and works as server/CLI kvim4: kernel panic during systemd-udevd khadas-vim4/khadas-vim1s: some fixes; VIM4/VIM4N now boots; workaround eMMC/oowow partition trouble for now vim1s/vim4: remove uEnv.txt and default extlinux args, use simple arguments instead meson-s4t7.conf: hack: rereadpt (re-read partition table) in initrd local-top (for eMMC boot of oowow'ed image) meson-s4t7.conf: include both u-boot.bin.sd.bin.signed and u-boot.bin.signed in uboot package meson-s4t7: patch kernel for different dt "model" across VIM4 and "New VIM4" meson-s4t7.conf: set EXTLINUX_SPECIFIC_FDT=no, so u-boot auto-determines which DTB to use don't specify DTB; this way both the "original VIM4" and the "new VIM4" can boot with the same image View the full article

Move the BPI-M2PRO off the BPI-M5 U-Boot. The BananaPi M5 supports the RTL8822CS Mezzanine, so let us provide the proper bluetooth firmware. NOTE: Boot needs verifying. 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 add PSI, ashmem, binder, binderfs to kernel config on meson64 to make Waydroid work on Amlogic S9xx. I just cherry-picked and copy/pasted changes from here: https://github.com/armbian/build/pull/4806 How Has This Been Tested? I build a ubuntu 22.04 image with Gnome, installed Waydroid, it works. View the full article

thinkpad-x13s: use steev's 6.3.y for working audio; fix Bluetooth; fix core temperature sensors; add modules & fw to initrd; pin & keep x13s PPA (fixes #5550) x13s: pin & keep x13s PPA (fixes #5550) x13s: initialize bluetooth's public-addr, thus allowing BT to work linux-arm64-sc8280xp.config: enable per-core temperature sensors x13s: disable snapd.seeded service so boot won't hang if clock's < 2017 (switching from Windows?) x13s: back to steev's 6.3.y, since 6.4.y's audio drivers don't match alsa-ucm-conf View the full article

Description Internal switch change. View the full article

As of today, NVK, the new Vulkan driver for Nvidia GPUs, has landed in the main Mesa branch and will be included as an experimental driver in the 23.3 release of Mesa. View the full article

Description One user on the forum (see https://forum.armbian.com/topic/27798-orange-pi-4-lts-default-thermal-trip-point-issues/) found issues with Orange PI 4 LTS thermal trip points. Looking into the problem, it is related to a patch introduced long time ago that changed the thermal trip points away from the vendor (and mainline kernel too) supplied ones. After some stress testing with openssl and mbw combined, my board froze and I had to shutdown it manually, let it cool and restart to have again a working system. It happens that, at least on my and forum user cases, the trip points are not doing what they expect to do. This patch corrects the trip points for Opi4 LTS: after repeating the same stress test, the kernel is capable of keeping the temperature under control without freezes Jira reference number AR-1812 How Has This Been Tested? [x] Tested device tree with trip points on live system [x] Patch applies correctly for rockchip64 current 6.1 kernel and does not break compilation 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

Add uart_A to the meson-sm1-bananapi-m2-pro DTS. 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

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 Maint. How Has This Been Tested? [x] Build test Checklist: [x] My changes generate no new warnings View the full article

Description Legacy - 5.15.123 -> 5.15.124 Current - 6.1.42 -> 6.1.43 Edge - 6.4.7 -> 6.4.8 Toggled CONFIG_RCU_TRACE in linux-sunxi-current.config to fix booting on 32-bit kernel 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] Booted legacy, current and edge images on Orange Pi Prime (sun50i H5) [X] Booted legacy, current and edge images on NanoPi Duo2 (sun8i H3) 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 As per subject, by forum user request - nothing fancy, just an ID added to some source code files How Has This Been Tested? [x] Compiled current 6.1 kernel [x] Compiled edge 6.4 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

At Collabora, we're committed to bringing people together. That's why we're pushing state-of-the-art machine-learning techniques like Large Language Models, Speech Recognition, and Speech-Synthesis techniques. View the full article

Linux 6.1 (current) / 6.4 (edge) Add "current" to: config/boards/bananapim2pro.csc Add uart_AO_B and uart_B to: meson-sm1-bananapi.dtsi Add related pins to: meson-g12-common.dtsi Add wif/bt support to: meson-sm1-bananapi-m5.dts (BT = uart_A) Add the ability to enable via overlays NOTE: The overlay to enable the wifi on the BPI-M5 will be added at a later date. 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 rockchip64 family edge kernel to 6.4. All enabled patches from 6.3 have been ported from to 6.4, some of them have been reworked/adapted. Jira reference number AR-1810 How Has This Been Tested? [x] Patches apply cleanly [ ] kernel compiles 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

hashed-OCI-revisioned-debs: introduce "reversioning" of .deb packages tl-dr: maximize OCI cache hit ratio across nightlies/releases/PRs/etc; publish simple Version:'s that don't include a crazy hash in repo and images introduce output/packages-hashed directory radically change the output/debs directory structure trap-logging: just discard logs dir when ANSI_COLOR=none repo-reprepro.py: set -e & pipefail prepare_host: handle PRE_PREPARED_HOST inside prepare_host_init() so WORKDIR etc is always available kernel-debs: avoid showing tree of kernel modules if they've not been built for example EXT=nomod causes no modules to be built debs: all produced debs now get a placeholder DEBIAN/changelog and a usr/share/doc .gz changelog with hash artifacts: don't keep deb-tar's .tar after uploading to OCI they won't ever be used after this, and just accumulate trash for no reason hashed-OCI-revisioned-debs: get completely rid of artifact_prefix_version hashed-OCI-revisioned-debs: build debs in PACKAGES_HASHED_STORAGE, not DEB_STORAGE (temp commit, will be rewritten by a later commit) fakeroot_dpkg_deb_build() now only takes a single argument, the unpacked package dir kernel/tmpfs: remove usage of the kernel-specific tmpfs for temporary kernel .deb's, now build directly to packages-hashed dir uboot: drop CHOSEN_UBOOT, change deployment directory, remove uboot_name as temp_dir prefix change deployment dir to not include REVISION or ARCH get rid uboot's CHOSEN_UBOOT, REVISION and ARCH in the directory name. no two u-boot debs can be installed in the same machine anyway pipeline: output-debs-to-repo-json.py: adapt to new reversioned JSON info hashed-OCI-revisioned-debs: introduce "reversioning" of .deb packages simplify artifact's prepare_version() method for deb and deb-tar artifacts: artifact_base_dir and artifact_final_file will now be auto-calculated; thus removed from each artifact (except rootfs) artifact_deb_repo ("global", "jammy", "bookworm") is now required; "global" means common across all RELEASES artifact_deb_arch is now required, "all" is arch-independent, otherwise use ${ARCH} artifact_map_debs is now auto-calculated based on the above, and shouldn't be specified manually artifact_final_version_reversioned is optional, and can force the final version of the artifact (specific for the base-files case) artifacts that need special handling for reversioning can add function names to artifact_debs_reversion_functions array (base-files and bsp-cli cases) artifacts prepare_version() should set artifact_version, but never include it in other variables; artifact_version is now changed by framework after prepare_version() returns no longer use/refer/mention ${REVISION} when building packages. All packages should be ${REVISION}-agnostic. ${REVISION} (actually, artifact_final_version_reversioned) will be automatically swapped in the control file during reversioning fakeroot_dpkg_deb_build() now takes exactly two arguments: the directory to pack, and the deb ID (key of artifact_map_packages dict); add this change in all the artifact's code for this obtain_complete_artifact(): automatically adds -Rxxxx "revisioning-hash" to artifact_version, by hashing the revisioning functions and any artifact_debs_reversion_functions set calculates more complex subdirectory paths for both the output/packages-hashed and output/debs/output/debs-beta directories with the new subdirectories we can be sure a re-version is already done correctly and can skip it (eg, for partial download-debs re-runs) in the future we can automatically clean/remove old versions that are no longer relevant based on the dir structure exports a lot more information to JSON, including the new subdirectory paths comment-out code that implemented skip_unpack_if_found_in_caches, I'm very unsure why we had this in the first place obtain_artifact_from_remote_cache() for deb type artifacts, OCI won't preserve the subdirectory structure, so move downloaded files to the correct subdirectory manually this is not needed for deb-tar, since that can preserve the dir structure itself introduce artifacts-reversion.sh and its main function artifact_reversion_for_deployment() this has the logic for reversioning .deb's, by ar-unpacking them, changing control.tar (and possibly data.tar), handling .xz compression, etc. also handles hashing those functions, for consistency. Any changes in reversioning code actually change the artifact itself so we're not caught by surprise by default, it changes control file only: replace Version: (which is the hash-version originally) with artifact_final_version_reversioned (which is mostly just ${REVISION}) add a custom field Armbian-Original-Hash: with the original hash-version artifact_reversion_for_deployment() is called by new CLI wrapper cli_obtain_complete_artifact(), used for CLI building of specific artifact, but also for download-artifact build_artifact_for_image() used during image build armbian-bsp-cli-deb.sh: move ${REVISION} related stuff from the main package build to new reversioning functions. artifact-armbian-base-files.sh: move ${REVISION} related stuff from the main package build to new reversioning functions. kernel: add some custom fields to DEBIAN/control: Armbian-Kernel-Version: / Armbian-Kernel-Version-Family: (for future use: cleanup of usage of Source: field which should be removed) declutter the Description: field, moving long description out of the first line obtain IMAGE_INSTALLED_KERNEL_VERSION from the reversioned deb (this is still a hack and has not been fixed) uboot: declutter the Description: field, moving long description out of the first line use the reversioned .deb when deploying u-boot to the image main_default_build_packages() now stores reversioned values and complete paths to reversioned .deb's list_installed_packages() now compares custom field Armbian-Original-Hash: , and not the Version: to make sure debs in the image are the ones we want install_artifact_deb_chroot() is a new wrapper around install_deb_chroot() for easy handling of reversioned debs use it everywhere install_deb_chroot() was used in distro-agnostic.sh and distro-specific.sh Signed-Off-By: Ricardo Pardini ricardo@pardini.net View the full article

Linux 6.1 (current) / 6.4 (edge) Add "current" to: config/boards/bananapim2pro.csc Add uart_A uart_AO_B and uart_B to: meson-sm1-bananapi.dtsi Add related pins to: meson-g12-common.dtsi Add the ability to enable via overlays 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