RSS Bot

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

Description This reverts commit 78aa57982efe523da9b52c15b2f3a423f8246390 as it breaks somewhere. View the full article

Description ARM_PSCI_CPUIDLE is not enabled in media boardfamily previousely. [ 3.141431] psci_checker: cpuidle not available on CPU 0, ignoring [ 3.141987] psci_checker: cpuidle not available on CPU 1, ignoring [ 3.142539] psci_checker: cpuidle not available on CPU 2, ignoring [ 3.143091] psci_checker: cpuidle not available on CPU 3, ignoring [ 3.143642] psci_checker: cpuidle not available on CPU 4, ignoring [ 3.144229] psci_checker: cpuidle not available on CPU 5, ignoring Enabling CPU idle can lower CPU power at low load, as well as killing these warning messages. How Has This Been Tested? [x] boot normally (testers x2) [x] stable at running 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 Thanks to NicoD giving me a kick, identified/implemented fix present in 6.2+ builds to keep the hub from going to suspend. How Has This Been Tested? Boot and USB 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 Hello all, This PR adds support for the Texas Instruments SK-AM62B. Features, schematics, and purchase links can be found on the board page[0]. This board is similar to the already supported SK-AM64B board but with a AM62 SoC. One big difference being the AM62 has a display controller and a GPU (IMG AXE-1-16M). Unfortunately the display controller driver is still being upstreamed and is not supported in the v6.4 kernel, so desktop support will have to wait until that is finished, we set HAS_VIDEO_OUTPUT to "no" for now. Thanks! [0] https://www.ti.com/tool/SK-AM62B Depends on #5543 and #5544 How Has This Been Tested? [x] Build/Boot tested Bookworm CLI/Minimal on Edge(v6.4) kernels [x] Build/Boot tested Jammy CLI/Minimal on Edge(v6.4) kernels [x] Dual Gbit Ethernet works 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 Update to the latest v6.4 kernel when using "edge" on K3 family devices How Has This Been Tested? [x] Tested on SK-TDA4VM, SK-AM62B, and SK-AM64B boards 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

The default will align the data structures with the cluster size, which causes the size to not be set to the full partition size. This causes issues with some board ROMs. Use the -a flag to ignore the alignment and fill the available space. How Has This Been Tested? [x] Tested on SK-TDA4VM, SK-AM62B, and SK-AM64B boards 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 Mainline updated the opp table handles to match the schema, this broke the overlays. https://github.com/torvalds/linux/commit/a30f3d90e2d2f4d0452c0f6f77693d0e9bba3b1e Overlays updated with corrected handle names. reported-by: @neofeo How Has This Been Tested? rk3399 successful application of overlays 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

rockchip ATF M0 code should use "arm-none-eabi-" toolchain to compile. "arm-linux-gnueabi-" toolchain causes LD error. Description When building rk3399 ATF, following error pops up when linking M0 codes. error: PHDR segment not covered by LOAD segment How Has This Been Tested? After this change, rk3399 ATF build passes. 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

No descriptionView the full article

Description As reported here, the cryptroot functionality was broken on boards that were using flash-kernel. Also because the dropbear config directory and filename is changed in newer dropbear versions, the ssh unlock functionality was broken on bullseye+. This PR fixes the same Jira reference number AR-1799 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 by creating image for RPI4B with cryptroot and ssh unlock enabled. Unlocked cryptroot using ssh key 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

I have been working on getting U-boot upstream up to speed for the Radxa Rock-5B Rockchip RK3588 board. One of the cool features that I recently published upstream is the ability to boot the board without any kind of non-volatile media (NVM) used. 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 Previous help message armbianmonitor -h Usage: armbianmonitor [-h] [-b] [-c $path] [-d $device] [-D] [-m] [-p] [-r] [-u] ############################################################################ Use armbianmonitor for the following tasks: armbianmonitor -c /path/to/test performs disk health/performance tests armbianmonitor -d monitors writes to $device armbianmonitor -D tries to upload debug disk info to improve armbianmonitor armbianmonitor -m provides simple CLI monitoring - scrolling output armbianmonitor -M provides simple CLI monitoring - fixed-line output armbianmonitor -n provides simple CLI network monitoring - scrolling output armbianmonitor -N provides simple CLI network monitoring - fixed-line output armbianmonitor -p tries to install cpuminer for performance measurements armbianmonitor -r tries to install RPi-Monitor armbianmonitor -u tries to upload armbian-hardware-monitor.log for support purposes armbianmonitor -v tries to verify installed package integrity armbianmonitor -z runs a quick 7-zip benchmark to estimate CPU performance ############################################################################ proposed change, attemts to follow the conventions commonly used for displaying a help message. armbianmonitor.sh" -h Usage: armbianmonitor.sh [-h] [-b] [-c $path] [-d $device] [-D] [-m] [-p] [-r] [-u] Options: -c /path/to/test Performs disk health/performance tests -d Monitors writes to $device -D Tries to upload debug disk info to improve armbianmonitor -m Provides simple CLI monitoring - scrolling output -M Provides simple CLI monitoring - fixed-line output -n Provides simple CLI network monitoring - scrolling output -N Provides simple CLI network monitoring - fixed-line output -p Tries to install cpuminer for performance measurements -r Tries to install RPi-Monitor -u Tries to upload armbian-hardware-monitor.log for support purposes -v Tries to verify installed package integrity -z Runs a quick 7-zip benchmark to estimate CPU performance no expected chaneg in behavero other then help output funtions -z was tested Checklist: [ ??] My code follows the style guidelines of this project [ Y] I have performed a self-review of my own code [ Y] I have commented my code, particularly in hard-to-understand areas [ NA] I have made corresponding changes to the documentation [ No] My changes generate no new warnings [ NA] Any dependent changes have been merged and published in downstream modules View the full article

Description It depends on https://github.com/armbian/linux-rockchip/pull/76 https://github.com/armbian/build/pull/5519#pullrequestreview-1549880906 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. [ ] Test A [ ] Test B 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 Update odroidxu4-current kernel to 5.4.251. I am not sure if the patches fixing the wireless drivers are the correct way of handling this, please feel free to ignore this PR if they are not. 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

Linux 6.1.y (current) / Linux 6.4.y (edge) meson-g12a-radxa-zero-gpio-10-led.dtbo (rev 1.51 enable led) meson-g12a-radxa-zero-gpio-8-led.dtbo (rev 1.4 enable led) meson-g12b-odroid-n2-spi.dtbo (SPI-NOR enable via overlay) 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 Bumped kernel versions as follows sunxi & sunxi64: legacy - 5.15.121 -> 5.15.123 edge - 6.4.5 -> 6.4.7 sunxi64 only: current - 6.1.40 -> 6.1.42 The sunxi current kernel is kept back as 6.1.42 is currently not booting on 32-bit allwinner 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] Booted updated sunxi images on NanoPi Duo2 (sun8i H3) [X] Booted updated sunxi64 images on Orange Pi Prime (sun50i H5) 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 fxblox-rk1 rk3588 board How Has This Been Tested? 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