RSS Bot

GStreamer 1.24 was recently released, and with it came with a new plugin to help separate pipelines into different processes. View the full article

Seattle is hosting this year's Embedded Open Source Summit, the umbrella conference for a collection of open source events. This is the premier space for the open source community and we'll be there with 6 talks! View the full article

This skips all git checkout, patching, configuring and cleaning when USE_EXISTING_KERNEL_TREE=yes is passed. This can be useful when doing kernel development by making changes directly to the kernel sourcetree in cache/sources, while still allowing to use the compile.sh to use the same compilation commands, deb package building, ccache, etc. It is also useful when bisecting a kernel issue. Can be used something like this: USE_EXISTING_KERNEL_TREE=yes ./compile.sh default kernel To produce a kernel deb in a few minutes ready to be installed on a device. This is mostly a proof of concept to explore the usecase. In particular: I am not happy with the USE_EXISTING_KERNEL_TREE name yet. I wonder if this variable should maybe be split into different ones (e.g. for skipping git checkout, patching, config, clean already has one that can be used). Or maybe it would be better to split off some code out of compile_kernel() and expose a kernel_build and/or kernel_package command from ./compile.sh instead? View the full article

Honoring outstanding innovations in the field of embedded system technologies, the annual Embedded Award ceremony will be taking place next week at Embedded World 2024 in Nuremberg. View the full article

As we reflect on the strides made in recent months, it's remarkable to see how OpenXR and Monado have evolved and are shaping the future of XR development. Let's take a closer look at the progress made and noteworthy achievements. View the full article

RFC: DO NOT MERGE: patching: rewrite: try to stabilize patch index stanzas as well as From lines RFC: DO NOT MERGE: patching: rewrite: try to stabilize patch index stanzas as well as From lines git format-patch --zero-commit doesn't affect index xxx...yyy lines, only From: so use the classy "use a regex with a callback" solution as git format-patch doesn't offer one this will make all patches change when rewritten, but hopefully for the last time ! not sure what other impacts this might have though - git am might not work any more? we need to preserve index 000000000000..xxx as zeros, which indicate new file creation, thus: new file creations are rewritten as index 000000000000..111111111111 non-creations are rewritten as index 111111111111..222222222222 DO NOT MERGE: Example rewrite of a patch with both file change & file creation View the full article

Description Fixes compilation for meson-s4t7. Had to enable DEBUG_KERNEL to fix Khadas vendor common_drivers. Apparently they won't compile without DEBUG stuff. Beware: This is the only SOC with DEBUG_KERNEL enabled now. See discussion here: https://github.com/armbian/build/commit/01be9ecbf9773dde94e089a852c3037e0daf0a9f How Has This Been Tested? [x] ./compile.sh kernel BOARD=khadas-vim1s BRANCH=legacy 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] My changes generate no new warnings View the full article

Description Add support to OrangePi Zero 2W (allwinner H618), changes: Patch for u-boot v2024.04-rc5, includes: allwinner-h616-THS-workaround.patch allwinner-h616-GPU-enable-hack.patch allwinner-pwrled-config-option.patch allwinner-enable-autoboot-keyed.patch allwinner-boot-splash.patch Kernel patch for adding zero2w dts, some part are taken from the orange pi official repo. Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: [ ] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) 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 and install the current image to SD, and then test on zero2w [x] Build and install the edge image to SD, and then test on zero2w [x] HDMI: test if HDMI output correctly [x] Network: test if wifi connect to access point correctly [x] Uart: test uart0 to get the kernel output [x] USB: test onboard type-c (host) [x] USB: test onboard type-c (otg) [x] USB: test usb port on the 24pin connector [x] GPIO: test GPIO voltage level - pull down and pull up by gpioset, both ok Checklist: Please delete options that are not relevant. [ ] 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

rockchip64-edge (6.8.y): enable CONFIG_RTW88_PCI and all the RTW88 PCI cards rockchip64-edge (6.8.y): enable CONFIG_RTW88_PCI and all the RTW88 PCI cards needed for the Tinkerboard-2 (8822CE) didn't touch SDIO or USB ones View the full article

Description Update odroidxu4-current kernel to 6.1.83. 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 [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 Two kernel branches have been added to 8250, as some of its features were compromised in 6. x, the latest branch is needed for testing Jira reference number [AR-9999] How Has This Been Tested? Both kernels were compiled on UMI and passed [x] Legacy [x] Edge Checklist: Please delete options that are not relevant. [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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Update shellcheck to version 0.10.0 which was released a few weeks ago. How Has This Been Tested? [x] sudo lib/tools/shellcheck.sh Output: Running shellcheck version: 0.10.0 against 308 config files, severity 'SEVERITY=error', please wait... Congrats, no error's detected in config/sources. Running shellcheck version: 0.10.0 against 'compile.sh' -- lib/ checks, severity 'SEVERITY=critical', please wait... All params: --check-sourced --color=always --external-sources --format=tty --shell=bash --severity=warning --exclude=SC2034 --exclude=SC2207 --exclude=SC2046 --exclude=SC2086 --exclude=SC2206 Congrats, no critical's detected in lib/ code. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description armsom-sige7: enable gpu rock-5a: enable gpu, fix poweroff, enable pcie2x1 for M.2 E slot hinlink-h88k: enable gpu 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] ./compile.sh kernel BOARD=armsom-sige7 BRANCH=edge DEB_COMPRESS=xz [x] Tested with armsom-sige7, rock-5a and hinlink-h88k Checklist: Please delete options that are not relevant. [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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Changes upstream rarely match exactly what is happening this far downstream. So let's take control by moving the old and patching a new. This gives us more freedom to make edits when we want or need to and avoid errors. View the full article

Description The issue When using ./compile.sh rewrite-kernel-config and then running the menuconfig with ./compile.sh kernel-config, just exiting and saving without any manual changes, the kernel config may still change. This is because rewrite-kernel-config does force some kernel options without any additional checks e.g. for dependencies. Using the config menu with kernel-config does those checks automatically and solves all dependencies. Example: Using ./compile.sh kernel-config on linux-rockchip64-edge.config (e.g. with BOARD=nanopi-r5c), the option CONFIG_DEBUG_KERNEL=y is automatically selected, since it is a dependency for CONFIG_EXPERT=y, which is selected in this kernel config as well. But then, ./compile.sh rewrite-kernel-config forces CONFIG_DEBUG_KERNEL to disabled. However, this breaks the dependency for CONFIG_EXPERT=y, which is still enabled. In consequence, CONFIG_DEBUG_KERNEL will be set to =y next time anyone runs ./compile.sh kernel-config on this config. The goal Doing a kernel-config (with no manual changes, just start and exit with saving) or a rewrite-kernel-config should lead to the exact same config file. It should be consistent. The solution This PR tries to solve this in the following way: Save the config right after the forced configs were applied Do an oldconfig after forced configs were applied to have kernel make solve any issues (will add ~3 seconds on each rewrite-kernel-config) Let the user see what was changed by kernel make so changes can be made accordingly Changes in forced kernel options by armbian-kernel.sh Set DEBUG_INFO_NONE=y instead of DEBUG_INFO=n since the latter is not configurable Remove GDB_SCRIPTS=n since DEBUG_INFO_NONE=y already implies this Example output in build log (for rk3588-legacy kernel): [🚸] Forced kernel options introduced misconfigurations or missing dependencies! [ Please re-run rewrite-kernel-config ] [🚸] If this warning persists [ please remove dependent options using kernel-config or adapt your custom_kernel_config hooks ] [🐛] In some cases, the issue might also be [ misconfigured options in armbian_kernel_config hooks ] [🔨] -DEBUG_INFO_NONE y [🔨] -MODULE_COMPRESS_NONE y [🔨] DEBUG_KERNEL n -> y [🔨] EXPERT n -> y [🚸] See options above which have been changed automatically [ to solve dependencies and/or misconfigurations ] As you can see, some of the forced kernel options did not have the expected results since kernel make had to change these to solve dependencies and make the config sane. Warning: This will output lots of changes on the first time it runs. Re-run it, the second run will output only the relevant changes. Some kernel configs will have to be adapted to solve the issues which are output in the warnings (like above), or armbian-kernel.sh might have to be adapted a bit linux-rockchip64-edge.config is an example, I just ran rewrite-kernel-config on this and kernel make did its magic. Overall, this should lead to more sane kernel configs. How Has This Been Tested? [x] rewrite-kernel-config for nanopi-r5c-edge [ ] Other kernels should be tested as well 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] My changes generate no new warnings View the full article

Description See title. This fixes kernel compilation for 6.8.2 How Has This Been Tested? [x] Apply wireless patches to rockchip64-edge (which is 6.8) Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description GitHub job summaries do not support colored output, but the kernel hardening script is using colored output. Thus, the job summary in the Actions panel is littered with ugly characters. This commit replaces them with emojis to enhance visibility. Before: After: How Has This Been Tested? [x] run locally: kernel-hardening-checker -m show_fail -c linux-rockchip64-edge.config | sed 's/^/ /; s/\x1b\[32m/✅ /; s/\x1b\[31m/❌ /; s/\x1b\[0m//' 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 View the full article

Description This PR refreshes OPP patches from kernel mailing list and adds automatic fan control support to Khadas Edge 2. Jira reference number [AR-9999] How Has This Been Tested? [x] Fan trip points have been tested. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Add GPU support to Khadas Edge 2 and add support for more display resolutions. Jira reference number [AR-9999] How Has This Been Tested? [x] Built and booted View the full article

Description As per subject, bump rockchip64 edge kernel to 6.8 Some patches have been reworked (helios64, nanopi-r2s, rockpi-s) to accomodate minor changes. Also this PR carries the same Makefile patch that was missing in tools/cgroup directory as well as https://github.com/armbian/build/pull/6429 Jira reference number AR-2112 How Has This Been Tested? [x] Kernel .deb compilation [ ] Live test kernel on rk3399 board [ ] Live test kernel on rk3328 board 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] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules (requires https://github.com/armbian/build/pull/6431 to be merged to properly compile, or EXTRAWIFI=no) View the full article

Description Little fixes to uwe5622 missing headers. This will make the driver compile on kernel 6.8 How Has This Been Tested? [x] Module compiles on edge kernel 6.8 [x] Module compiles on current kernel 6.6 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description Missing &vop node makes hdmi not work, add it. 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] ./compile.sh kernel BOARD=armsom-sige7 BRANCH=edge DEB_COMPRESS=xz [x] hdmi works Checklist: Please delete options that are not relevant. [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 [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, bump edge kernel to 6.8 for rockchip 32 bit family. Also include a patch to handle an apparently missing Makefile in tools/cgroup directory which makes the compilation process crash when cleaning the tools kernel subdirectory. In case other families are bumped to kernel 6.8, it should be copied as well or moved into misc directory and applied somewhere until kernel people fix that. Jira reference number AR-2111 How Has This Been Tested? [x] Kernel .deb packages compiled and tested on a rk322x-box live system 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] My changes generate no new warnings View the full article

Description As described in the forum topic https://forum.armbian.com/topic/35677-tinkerboard-not-booting-after-updates/#comment-185896, upgrading on Asus Tinkerboard breaks the bootloader and prevents the entire system to reboot. As side effect - but not yet reported by anyone - should also break other rk3288 and rk322x board bootloaders. This PR restores the previous post-install platform_install.sh script for each board/family as it was before the family merge. Jira reference number AR-2109 How Has This Been Tested? [x] Compiled tinkerboard target, extracted the u-boot .deb package and manually inspected platform_install.sh script, not tested on a live system [x] Compiled rk322x-box target, extract u-boot .deb package and manually inspected platform_install.sh script 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] My changes generate no new warnings View the full article

Description As mentioned by @andyshrk , this gpu node patch has deleted line status = "disabled"; of node usb_host2_xhci, this will fix that so usb_host2_xhci will not get enabled on all 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] ./compile.sh kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow [x] Check node usb_host2_xhci in file cache/sources/linux-kernel-worktree/6.8__rockchip-rk3588__arm64/arch/arm64/boot/dts/rockchip/rk3588s.dtsi [x] rock5b boots fine Checklist: Please delete options that are not relevant. [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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article