RSS Bot

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

Description This set of changes tries to handle the requirement of reducing cache misses by removing the REVISION prefix from the tag of the OCI cache. It works by making use of a tag that doesn't include the version prefix. Once the artifact is fetched, if the filename is not what we expect, then the file is renamed to the expected file name. This can be required in cases when REVISION is bumped but no changes are done for the artifact. In that case, for example, we might be looking for a artifact with version 23.08.1-trunk prefix while the artifact thats available and is identical to the needed artifact might have version starting with 23.08.0-trunk. Only the OCI tags are changed and files are renamed when needed, deb files are not modified in anyways in this solution. Also quick testing shows that it works fine. But I am going to do some more testing tomorrow and then will remove the WIP prefix. 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] Removed all debs and docker volumes. Then compiled an image followed by uploading of the artifact to OCI using ./compile.sh <artifact_name> OCI_TARGET_BASE=172.17.0.2:5000/. Then removed all debs and changed VERSION file. Then rebuilt the image and checked that artifacts are fetched from OCI cache 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

pipeline: debs-to-repo-download is now done in parallel; default cores*2 limited to 16 or PARALLEL_DOWNLOADS_WORKERS pipeline: debs-to-repo-download is now done in parallel; default cores*2 limited to 16 or PARALLEL_DOWNLOADS_WORKERS also avoid log archiving during individual download jobs via SKIP_LOG_ARCHIVE=yes I've tested with PARALLEL_DOWNLOADS_WORKERS=16 and it saturates my gigabit link, ghcr.io is great at reads more than ~16-ish might be too much though View the full article

display-alert: strip newlines as well as ANSI colors if ANSI_COLOR=none display-alert: strip newlines as well as ANSI colors if ANSI_COLOR=none ANSI_COLOR=none is used when we're driving compile.sh from Python some debugging messages had newlines in them, thus making Python mark those as [LEAKED] View the full article

armbian-desktop/aggregation: introduce DESKTOP_COMMON aggregation variant, where arch/config/appgroups are ignored; see #5439 (re-submitted) armbian-desktop/aggregation: introduce DESKTOP_COMMON aggregation variant, where arch/config/appgroups are ignored; see #5439 (re-submitted) this has been tested with complete/default targets and works View the full article

kernel / drivers-harness: use the kernel git SHA1 ($KERNEL_GIT_SHA1) instead of $KERNEL_MAJOR_MINOR for drivers cache key kernel / drivers-harness: use the kernel git SHA1 ($KERNEL_GIT_SHA1) instead of $KERNEL_MAJOR_MINOR for drivers cache key this should avoid (late) patching errors that might happen during a point release bump like 6.4.5 -> 6.4.6 cos we'd be using the wrong cached drivers patch using the SHA1 will instead (possibly) trigger the "real patching failure", during drivers-harness when building a new driver patch cache also try to cleanup old caches in the old format so we've not many leftovers -- each patch is ~150mb View the full article

meson64/rockchip64 current/edge: enable CONFIG_NVME_HWMON=y for NVMe temperature monitoring linux-rockchip64-current.config / linux-rockchip64-edge.config: update config, no changes linux-rockchip64-current.config / linux-rockchip64-edge.config: enable CONFIG_NVME_HWMON=y for NVMe temperature monitoring linux-meson64-current.config / linux-meson64-edge.config: update config, no changes linux-meson64-current.config / linux-meson64-edge.config: enable CONFIG_NVME_HWMON=y for NVMe temperature monitoring View the full article

If you weren't able to attend Embedded Open Source Summit in Prague last month, you're in luck as all presentations were recorded and are now available on YouTube. View the full article