RSS Bot

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

Description Removing deprecated patches How Has This Been Tested? [x] Patching works now 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 Tinkerboard 2 SOC uses the weird baudrate 1500000 for debug uart. and the1500000 is not supported by most of the serial terminal application. Here change the baudrate from 1500000 to 115200 which is the most common baudrate for debug uart How Has This Been Tested? tested with tinkerboard 2s, and able to see the correct bootloader console message. View the full article

Description add fxblox-rk1 board base on RK3588 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 Add LED's, fusb302 (doesn't do anything yet), theoretical sound card support. 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. builds/boots, lights flash 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

After months of work, led by Collabora's own Faith Ekstrand, Red Hat's Karol Herbst, and numerous open source contributors, NVK is now considered ready to be merged into the main Mesa project. View the full article

Description Found we had cvbs support for allwinner H3 for current kernel. It had bits to make it working for H5 as well with only thing missing was the overlay to enable the it. Hence added the overlay for H5. Also as the patch was missing in edge kernel, added the same. 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] Created a server image for OrangePi Prime and attached a CVBS/AV display to it. The console was also shown on the AV monitor. 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

pipeline: inventory all board vars; add not-eos-with-video; introduce TARGETS_FILTER_INCLUDE pipeline: inventory all board vars; add not-eos-with-video; introduce TARGETS_FILTER_INCLUDE How to use: ./compile.sh inventory - does just the board inventory; look for output in output/info ./compile.sh targets-dashboard - does inventory, targets compositing, and images info; look for output in output/info, read the instructions output by the command if you want to load the OpenSearch dashboards. ./compile.sh targets - does the full targets compositing and artifacts, look for output in output/info If you don't have a userpatches/targets.yaml, one will be provided for you defaulting to Jammy minimal CLI and Jammy xfce desktop, for all boards in all branches. You can pass filters via TARGETS_FILTER_INCLUDE=... to narrow. board JSON inventory: more generic regex parsing of variables from board files: all top-level (non-indented) variables are parsed and included in the JSON board inventory this allows us to add new variables to the board files without having to update the parser variables can be bare, export or declare -g, but must be quoted (single or double) and UPPER_CASE some special treatment for certain variables: KERNEL_TARGET is parsed as a comma-separated list of valid BRANCH'es BOARD_MAINTAINER is parsed as space-separated list of valid maintainer GH usernames as BOARD_MAINTAINERS: [...] in the JSON script complains if BOARD_MAINTAINER is not set in core boards. Empty is still allowed. HAS_VIDEO_OUTPUT="no" causes BOARD_HAS_VIDEO: false in the JSON (for desktop-only inventorying, see below) introduce not-eos-with-video in items-from-inventory at the targets compositor the same as not-eos, but with added BOARD_HAS_VIDEO: true filter, see above introduce TARGETS_FILTER_INCLUDE for targets compositor this filters the targets after compositing (but before getting image info), based on the board inventory data it's a comma-separated list of key:value pairs, which are OR-ed together new virtual info BOARD_SLASH_BRANCH post-compositing inventory for filtering of a specific BOARD/BRANCH combo (e.g. odroidhc4/edge) some interesting possible filters: TARGETS_FILTER_INCLUDE="BOARD:odroidhc4": only build a single board, all branches. JIRA AR-1806 TARGETS_FILTER_INCLUDE="BOARD_SLASH_BRANCH:odroidhc4/current": only build a single board/branch combo TARGETS_FILTER_INCLUDE="BOARD:odroidhc4,BOARD:odroidn2": only build two boards, all branches. TARGETS_FILTER_INCLUDE="BOARD_MAINTAINERS:rpardini": build all boards and branches where rpardini is a maintainer TARGETS_FILTER_INCLUDE="BOARDFAMILY:rockchip64": build all boards and branches in the rockchip64 family image-info-only variables like LINUXFAMILY is not available for filtering at this stage rename config/templates targets-all-cli.yaml to targets-default.yaml this is used when no userpatches/targets.yaml is found new default includes all boards vs branches for non-EOS boards also desktop for all boards that don't have `HAS_VIDEO_OUTPUT='no`` introduce simplified targets-dashboard CLI: does only inventory, compositing, and image info, but not artifact reducing, etc. ignore desktop builds in the OpenSearch indexer update the OpenSearch Dashboards, including new information now available invert the logic used for CLEAN_INFO and CLEAN_MATRIX defaults to yes now, so new users/CI don't get hit by stale caches by default repo pipeline CLI stuff is usually run on saved/restored artifacts for output/info, so don't clean by default via the CLI View the full article

config/boards: fix some missing quotes / maintainers config/boards: fix some missing quotes / maintainers View the full article

rk3399: legacy .config for rk3399 was removed long ago; completely drop rk3399 family, move boards to rockchip64 and remove their legacy KERNEL_TARGET rk3399: legacy .config for rk3399 was removed long ago; completely drop rk3399 family, move boards to rockchip64 and remove their legacy KERNEL_TARGET also drop hooks referring to legacy View the full article

linux-rk35xx-legacy.config: enable VHOST_NET and others for hosting VM's linux-rk35xx-legacy.config: enable VHOST_NET and others for hosting VM's View the full article