RSS Bot

Welcome to your weekly dose of Armbian insights. From thermal management to industry trends, here's what the community is talking about this week. GitHub Highlights GitHub highlightsWeekly Armbian development highlights including expanded board support for DshanPi A1, Raspberry Pi kernel updates to 6.16, and build system improvements.Armbian blogMichael RobinsonHands-on ! Self-host your photos with Immich and ArmbianImmich is a sleek, self-hosted alternative to Google Photos offering powerful features like mobile uploads, facial recognition, and full privacy. With Armbian, setting it up on your own device is simple and efficient.Armbian blogInella JoomunTips & tricks Power mattersWhy choosing the correct input voltage and stable power supply is important for your single board computer’s reliability.Armbian blogMichael RobinsonStay coolWhy heatsinks are essential for SBC performance and longevity.Armbian blogMichael RobinsonState of the SBC & embedded computing industry (2025)The SBC and embedded computing market is projected to reach $3.6 billion by 2030, growing at 6-7% annually. ARM systems dominate with 40% market share, while RISC-V emerges as a compelling open-source alternative.Armbian blogMichael RobinsonThat's a wrap for this week's Armbian updates. Keep your boards cool, your power stable, and your projects running smoothly. Sign up for Armbian blog Embedded Linux, Open Source, and the Armbian Community Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. View the full article

Single Board Computers (SBCs) like the Orange Pi 5, Radxa Rock 5, and others powered by modern SoCs are more powerful than ever. But that performance comes with a cost heat. Without proper thermal management, these boards can throttle, crash, or suffer long-term damage. Whether you’re running a server, media center, or developer workstation, adding a simple heatsink can dramatically improve stability, performance, and device lifespan. Why heat is a problem for SBCsAll computers generate heat and SBCs are no exception. The CPU, GPU, RAM, and power management chips on an SBC work hard, and as a result, temperatures rise quickly under load. Unlike laptops and desktops, most SBCs lack active cooling. Many ship with no heatsink at all, relying entirely on the board’s surface area and ambient airflow for cooling. This may work fine for light workloads, but during high CPU or GPU use, it simply isn’t enough. When temperatures exceed a safe threshold (typically between 70°C and 95°C, depending on the chip), the system protects itself with thermal throttling automatically reducing CPU frequency to lower heat. In extreme cases, it may reboot or shut down entirely to avoid permanent damage. Thermal throttling: The silent performance killerThrottling is often subtle and can go unnoticed. Tasks may take longer, video playback may stutter, or system responsiveness may drop but without clear warning messages. Typical signs of thermal throttling include: CPU frequencies dropping significantly under loadSluggish performance during intensive tasksGradual degradation in responsiveness over timeThese symptoms are easy to misdiagnose as software issues. But in many cases, they can be resolved simply by cooling the SoC properly and that starts with a heatsink. Real-world example: Orange Pi 5 without a heatsinkConsider the Orange Pi 5 with the RK3588S SoC. Under sustained load, it can reach temperatures over 85°C. Without a heatsink, users commonly report: CPU throttling within 30–60 seconds of full loadUnstable system behavior during multitaskingIdle temperatures in the high 60s to low 70s °C in warm environmentsA basic aluminum heatsink can drop idle temperatures by 15–20°C and reduce load temperatures by 25–30°C. Larger finned models or full heatsink kits keep the board stable even during stress testing. Types of cooling solutionsPassive heatsinks: Made from aluminum or copper, these rely on surface area and ambient airflow to dissipate heat. They’re silent, durable, and usually sufficient for moderate loads.Active cooling (Heatsink + Fan): Adds a small fan to improve airflow across the heatsink. Great for keeping temperatures low under heavy load, but introduces noise and moving parts.Heatsink cases and enclosures: Some cases act as the heatsink themselves, with thermal pads that transfer heat from the SoC to the case. Others feature built-in fans and vents. Avoid sealed plastic enclosures that trap heat.Tips for effective heatsink useUse thermal interface material: A heatsink without thermal paste or a thermal pad is only half effective. Apply a thin, even layer to bridge the gap between the chip and the heatsink.Clean the SoC surface: Remove dust or residue with isopropyl alcohol to ensure good contact.Ensure proper mounting: The heatsink must make tight, flush contact with the chip. Loose or uneven mounting leads to poor cooling.Consider additional components: Some SBCs benefit from heatsinks on RAM, PMICs, or USB controllers especially if your workload is heavy or your board runs 24/7.Choose quality materials: Copper conducts heat better than aluminum, but aluminum is lighter and often sufficient. Large finned designs increase surface area and effectiveness.Why it mattersEffective cooling isn’t just about preventing crashes it preserves performance and extends hardware lifespan. Performance: A cooled CPU can maintain full frequency, giving you faster compile times, smoother video, and more responsive interaction.Stability: Preventing overheating reduces the risk of kernel panics, application errors, and filesystem corruption.Longevity: Prolonged heat exposure shortens the life of electronic components. Keeping things cool helps ensure your SBC runs reliably for years to come.ConclusionIf you’ve invested in a capable SBC, don’t let heat undermine your project. A simple heatsink often costing just a few dollars can unlock the board’s full potential and prevent hours of frustrating troubleshooting. Whether your SBC is headless or running a full desktop environment, thermal management is essential. Keep it cool, and your board will reward you with consistent, stable, and long-lasting performance. View the full article

Greetings, Armbian community! Here's a concise overview of the key developments and improvements merged into our build system this past week. HighlightsExpanded board support: We've added initial support for the DshanPi A1 (RK3576), broadening Armbian's reach to more hardware.Kernel updates: The edge kernel for Raspberry Pi 4B has been updated to 6.16, bringing the latest features and fixes to the platform.Build system robustness: Important adjustments were made to ensure more reliable U-boot source fetching and improved patch application processes.New featuresNew board and variant support:Add support for DshanPi A1 (RK3576) (#8380)Add BPI-M4-Zero to Sunxi64 device tree directory and enable related graphics drivers (#8394)Add current-rt branch support for PocketBeagle 2 (#8371)K3-Beagle series enhancements:Enable M4 remoteproc for linux-k3-beagle-current-rt (#8395)Enable M4 remoteproc for linux-k3-beagle (#8378)Sunxi64 general input support:Enable keyboard support (CONFIG_KEYBOARD_*) (#8387)Add touchscreen and miscellaneous input support (INPUT_TOUCHSCREEN and INPUT_MISC) (#8385)Bug fixesMeson64 Patch Adjustment: Adjusted a broken patch for Meson64 Current kernel configurations. (#8393)U-boot Source Fix: Resolved issues with fetching U-boot sources from the Denx Git repository. (#8402)Sunxi64 RTC Configuration: Updated defconfigs and addressed H616 RTC-related patches. (#8368)ImprovementsKernel version bump:Bump Raspberry Pi family edge kernel to 6.16 (#8390)Configuration refinements:Remove unused kernel configurations for a leaner build (#8392)Update CAN and CPU frequency configurations for Sunxi64 (#8383)Improve UEFI x86 current and edge defconfigs (#8367)Add cloud branch to UEFI arm64 board configuration (#8376)Documentation & aesthetics:Cleaned and updated the build repository README file, including a new logo. (#8391)Added the most recent Armbian logo as the Plymouth boot logo (#8381)Enabled Armbian auto-patching for Sunxi64 configurations (#8394)Community contributors@Ayush1325 @chainsx @EvilOlaf @igorpecovnik @pyavitz @ZjemCiKolege View the full article

Getting into kernel development can be daunting. There are layers upon layers of knowledge to master, but no clear roadmap, especially when it comes to debugging drivers or navigating userspace-kernel issues. View the full article

Immich is a high-performance, self-hosted photo and video backup solution, ideal for individuals and families seeking an alternative to cloud-based services like Google Photos or iCloud. It offers a private, secure space to store, browse, and share memories without sacrificing modern features or user experience. With Armbian, deploying Immich on single-board computers is easy whether you're using a RockPro64, Raspberry Pi, or Odroid running Armbian. What makes Immich stand out?Immich combines a sleek interface with powerful functionality: Automatic mobile uploads for seamless backupFacial recognition and machine learning search to organize contentMulti-user support for families or small teamsA modern web and mobile interface that feels familiar and intuitiveSupport for HEIC, RAW, and other formats photographers appreciateWhy use Armbian?Armbian provides a lightweight, optimized Linux environment for ARM-based boards. It’s stable, community-driven, and ideal for home server projects. Using armbian-config, installing software like Immich becomes a single-step operation. There's no need to manually clone repos, edit .env files, or orchestrate Docker Compose stacks. It's simply: Using armbian-config, installing Immich is as simple as: armbian-config → Software → Immich → Install That’s it. No Compose files, no manual setup. Uninstalling is just as quick. All containers use a centralized data storage path at /armbian, making backup and restore straightforward no need to go through scattered volumes or configs. This simplicity is built-in, so you can focus on your apps, not infrastructure. If you’re looking to break free from cloud dependence and run your own media solution, Immich on Armbian is a project worth exploring. Check the official Armbian guide here: Immich on Armbian View the full article

Choosing the right input voltage and ensuring stable power supply for SBCsWhen working with single board computers (SBCs) like those supported by Armbian, one of the most overlooked but critical factors for performance and system reliability is the power supply. Whether you're running a lightweight server, a development environment, or a complex home automation system, power instability can lead to frustrating and difficult-to-diagnose problems. Understanding the correct input voltage and ensuring a stable power supply is essential for the long-term health of your SBC. Why Power Supply Issues Are So CommonUnlike desktop systems that come with regulated internal power supplies, SBCs rely entirely on external power adapters. These small boards are expected to do a lot run desktop environments, manage network traffic, operate storage devices, or even handle video output and all of it depends on steady power. Many users assume that any 5V adapter or USB-C charger will suffice. This assumption often leads to problems like: Random rebootsFailed bootsUSB peripherals disconnectingSD card corruptionOverheating from inefficient voltage conversionWhat’s worse, these symptoms are often mistaken for software bugs, when in reality, the board is simply not getting the power it needs. The importance of voltage AaccuracyMost SBCs supported by Armbian require a 5V input, but not just any 5V. The tolerance for voltage drop is narrow often less than ±5%. A supply that delivers 4.75V under load may already be too low, especially when additional peripherals draw current. For boards like the Orange Pi 5/5 Plus or Rockchip RK3399-based systems, this becomes more critical. These boards include CPUs that demand bursts of current during processing spikes. If your power supply cannot maintain a solid 5.1–5.2V under load, you’ll start seeing intermittent failures or throttling. Boards that support USB-C PD (Power Delivery) can negotiate for higher voltage levels (e.g., 9V or 12V), but this only works correctly if the power supply and USB-C cable both support PD and follow the standard. If they don't, the board may only receive 5V or nothing at all. Current (Amperage) capacityVoltage is only half the story. You also need enough current (measured in amps, or A). For most SBCs: Lightweight boards (like Orange Pi Zero) require at least 1–2A.Mid-range boards (like Orange Pi 3 LTS, RK3328) should have at least 3A.High-performance boards (RK3588, RK3399, etc.) often need 4–5A, especially under load or when powering peripherals.A common mistake is to use a "fast charger" designed for phones. These may list high amperage (like 3A), but they rely on USB Power Delivery protocols. If the board doesn't negotiate the higher voltage profile, it may default to 5V @ 500mA which is far too low. How to test your power supplyThe best way to confirm your power supply is adequate is by using a multimeter or USB voltage/current meter: Check idle voltage: Connect the power supply to your board. Using a multimeter, probe the 5V and GND pins (or use a USB tester). You should see between 5.1V and 5.25V. Less than 5.0V is a warning sign.Test under load: Stress the CPU (e.g., with stress-ng or compiling software). Watch the voltage. A good supply should not drop below 5.0V. If it does, expect instability.Measure at the board, not the adapter: Long or thin cables can cause voltage drop even if your adapter is good. This is especially true with Micro-USB or low-quality USB-C cables. Always test at the input connector on the board itself.Recommendations for stable powerUse a quality PSU: Avoid generic adapters. Use brands known for clean power delivery (e.g., Mean Well, Anker, official Raspberry Pi or Orange Pi supplies). A 5V/4A supply with a barrel jack or PD support is ideal for high-end SBCs.Prefer barrel jack over Micro-USB: Micro-USB is notorious for unreliable power delivery due to thin connectors and cable resistance.Use short, thick cables: The longer the cable, the more voltage drops across it. Choose 18AWG or thicker cables, especially if using USB.Avoid USB hubs for power: Even powered hubs often introduce noise or underperform when multiple devices draw current.Monitor system logs: Look for undervoltage warnings in dmesg or Armbian’s armbianmonitor output. This is an early sign that your supply may not be sufficient.ConclusionPower issues are one of the leading causes of instability and hardware failure in SBC projects. Armbian users can save countless hours of troubleshooting by investing in a good power setup from the start. Always ensure you're providing the correct input voltage (typically 5.1–5.2V) and enough current (up to 4–5A for high-performance boards). Measure voltage under load, use high-quality adapters and cables, and stay vigilant for undervoltage signs. A stable SBC starts with stable power it’s the foundation of everything else. View the full article

The single-board computer (SBC) and embedded computing market is seeing steady expansion, with a projected valuation of $3.6 billion USD by 2030, growing at a compound annual growth rate (CAGR) of 6–7% ¹². Growth is largely driven by the rising demand for edge computing, IoT, industrial automation, and AI-enabled systems. ARM-based systems dominate the market due to their low power consumption and cost efficiency, accounting for over 40% of deployed SBCs ¹. However, RISC-V is emerging as a compelling open-source alternative, particularly in industrial and academic sectors, while x86 remains important for legacy and high-performance use cases ². Asia-Pacific leads global growth, particularly in China and India, due to smart infrastructure and 5G deployments. Meanwhile, North America remains dominant in terms of revenue share, especially in healthcare, defense, and industrial sectors ³. Key players like Raspberry Pi, Advantech, Kontron, and Hardkernel continue to innovate. Raspberry Pi Ltd., now a public company, reports that over 70% of its 68 million units sold are deployed in industrial or commercial use cases ⁴. View the full article

This past May, we met with the community at the GStreamer Spring Hackfest in Nice, France, and were able to make great strides, including the integration of AI/ML workflows in GStreamer. View the full article

Collabora is proud to sponsor this year's annual Debian conference, taking place in Brest, France. Join us as we showcase the latest with Apertis, discuss Debian running on mobile devices, and more. View the full article

The last year has seen substantial progress on the DRM infrastructure required to write GPU drivers in Rust. Developed in collaboration with Arm and Google, Tyr is a new Rust-based DRM driver targeting CSF-based Arm Mali GPUs. View the full article

As part of the activities Embedded Recipes in Nice, France, Collabora hosted a PipeWire workshop/hackfest, an opportunity for attendees to meet face-to-face with PipeWire developers and participate in direct discussions about the future of PipeWire. View the full article

This partnership ensures customers can build embedded products with long-term maintenance viability that will meet the challenges of tomorrow, such as compliance with the CRA, all built on proven Toradex platforms and upstream-first software. View the full article

In collaboration with Inria, the French Institute for Research in Computer Science and Automation, Tathagata Roy shares the progress made over the past year on the CoccinelleForRust project, co-sponsored by Collabora View the full article

Last month in Nice, active media developers came together for the annual Linux Media Summit to exchange insights and tackle ongoing challenges in the media subsystem. Here’s a brief summary of the key discussions and upcoming areas of focus. View the full article

Building on our Open Source strengths in AI and data-driven solutions, Collabora's ML team, led by Marcus Edel, Vineet Suryan, & Aaron Boxer, has taken first place in Track 3 of the ICME 2025 Grand Challenge on Video Super-Resolution for Video Conferencing. View the full article

Improving access, flexibility, and CI integration for development boards, making it easier for developers to work with embedded hardware, no matter where they are. View the full article

Bumps dtschema from 2025.2 to 2025.6.1. Commits 18ac2d8 validator: Fix ordering issue with properties referencing another property 4dbacd6 tests: Add test for DTSchema.check_schema_refs() 2c5f057 schema: Rework instantiating DTSchema.validator 19c88b9 schemas: gpio-nexus-node: Fix schema $ref paths fb770c7 schema: Fix a false positive unevaluatedProperties/additionalProperties check b7f612c schemas: reset: Add '#reset-cells' into schema 7e3ef3e schemas: reset: Add descriptions from original text binding 53a2132 meta-schemas: nodes: Allow if-then-else directly in patternProperties objects 9d1305d schemas: PCI: Add standard PCIe WAKE# signal 49451a5 schemas: root-node: Add 'all-in-one' chassis-type Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps oras from 0.2.33 to 0.2.37. Release notes Sourced from oras's releases. Oras Python v0.2.37 What's Changed Use correct credsStore/credHelpers binary by @rasmusfaber in oras-project/oras-py#212 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.36...0.2.37 Oras Python v0.2.36 What's Changed Fix authentication priority: AWS-native -> docker login -> credHelpers -> credsStore by @rasmusfaber in oras-project/oras-py#211 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.35...0.2.36 Oras Python v0.2.35 What's Changed fix: auth via ECR to be an extra by @tarilabs in oras-project/oras-py#208 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.34...0.2.35 Oras Python v0.2.34 What's Changed [tributors] contributors/update-2025-05-31 by @github-actions in oras-project/oras-py#203 Add support for Docker credsStore and credHelpers by @rasmusfaber in oras-project/oras-py#206 [tributors] contributors/update-2025-06-08 by @github-actions in oras-project/oras-py#207 Ecr auth support by @rasmusfaber in oras-project/oras-py#205 New Contributors @rasmusfaber made their first contribution in oras-project/oras-py#206 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.33...0.2.34 Changelog Sourced from oras's changelog. CHANGELOG This is a manually generated log to track changes to the repository for each release. Each section should include general headers such as Implemented enhancements and Merged pull requests. Critical items to know are: renamed commands deprecated / removed commands changed defaults backward incompatible changes (recipe file format? image file format?) migration guidance (how to convert images?) changed behaviour (recipe sections work differently) The versions coincide with releases on pip. Only major versions will be released as tags on Github. 0.0.x (0.0.x) Use the correct credsStore/credHelpers binary (0.2.37) Properly prioritize auth methods (0.2.36) fix 'authentication with ECR' to be an extra as intended (0.2.35) Add support for authentication with ECR registries (0.2.34) Add support for Docker credsStore and credHelpers fix 'get_manifest()' method with adding 'load_configs()' calling (0.2.33) fix 'Provider' method signature to allow custom CA-Bundles (0.2.32) initialize headers variable in do_request (0.2.31) Make reproducible targz without mimetype (0.2.30) don't include Content-Length header in upload_manifest (0.2.29) propagate the tls_verify parameter to auth backends (0.2.28) don't add an Authorization header is there is no token (0.2.27), closes issue 182 check for blob existence before uploading (0.2.26) fix get_tags for ECR when limit is None, closes issue 173 fix empty token for anon tokens to work, closes issue 167 retry on 500 (0.2.25) align provider config_path type annotations (0.2.24) add missing prefix property to auth backend (0.2.23) allow for filepaths to include : (0.2.22) release request (0.2.21) add missing basic auth data for request token function in token auth backend (0.2.2) re-enable chunked upload (0.2.1) refactor of auth to be provided by backend modules (0.2.0) bugfix maintain requests's verify valorization for all invocations, augment basic auth header to existing headers Allow generating a Subject from a pre-existing Manifest (0.1.30) add option to not refresh headers during the pushing flow, useful for push with basic auth (0.1.29) enable additionalProperties in schema validation (0.1.28) Introduce the option to not refresh headers when fetching manifests when pulling artifacts (0.1.27) To make it available for more OCI registries, the value of config used when manifest_config is not specified in client.push() has been changed from a pure empty string to {} (0.1.26) refactor tests using fixtures and rework pre-commit configuration (0.1.25) eliminate the additional subdirectory creation while pulling an image to a custom output directory (0.1.24) updating the exclude string in the pyproject.toml file to match the data type black expects patch fix for pulling artifacts by digest (0.1.23) patch fix to reject cookies as this could trigger registries into handling the lib as a web client ... (truncated) Commits 5d3c15d Use correct credsStore/credHelpers binary (#212) 385f138 Fix authentication priority: AWS-native -> docker login -> credHelpers -> cre... d296ffd fix: auth via ECR to be an extra (#208) 1d448f2 Ecr auth support (#205) dad7734 Automated deployment to update contributors 2025-06-08 (#207) 2a421e2 Add support for Docker credsStore and credHelpers (#206) b63ede0 Merge pull request #203 from oras-project/contributors/update-2025-05-31 6886229 Automated deployment to update contributors 2025-05-31 See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps tj-actions/changed-files from 4140eb99d2cced9bfd78375c2088371853262f79 to d52d20fa3f981cb852b861fd8f55308b5fe29637. Changelog Sourced from tj-actions/changed-files's changelog. Changelog 46.0.5 - (2025-04-09) ⚙️ Miscellaneous Tasks deps: Bump yaml from 2.7.0 to 2.7.1 (#2520) (ed68ef8) - (dependabot[bot]) deps-dev: Bump typescript from 5.8.2 to 5.8.3 (#2516) (a7bc14b) - (dependabot[bot]) deps-dev: Bump @types/node from 22.13.11 to 22.14.0 (#2517) (3d751f6) - (dependabot[bot]) deps-dev: Bump eslint-plugin-prettier from 5.2.3 to 5.2.6 (#2519) (e2fda4e) - (dependabot[bot]) deps-dev: Bump ts-jest from 29.2.6 to 29.3.1 (#2518) (0bed1b1) - (dependabot[bot]) deps: Bump github/codeql-action from 3.28.12 to 3.28.15 (#2530) (6802458) - (dependabot[bot]) deps: Bump tj-actions/branch-names from 8.0.1 to 8.1.0 (#2521) (cf2e39e) - (dependabot[bot]) deps: Bump tj-actions/verify-changed-files from 20.0.1 to 20.0.4 (#2523) (6abeaa5) - (dependabot[bot]) ⬆️ Upgrades Upgraded to v46.0.4 (#2511) Co-authored-by: github-actions[bot] (6f67ee9) - (github-actions[bot]) 46.0.4 - (2025-04-03) 🐛 Bug Fixes Bug modified_keys and changed_key outputs not set when no changes detected (#2509) (6cb76d0) - (Tonye Jack) 📚 Documentation Update readme (#2508) (b74df86) - (Tonye Jack) ⬆️ Upgrades Upgraded to v46.0.3 (#2506) Co-authored-by: github-actions[bot] Co-authored-by: Tonye Jack jtonye@ymail.com (27ae6b3) - (github-actions[bot]) 46.0.3 - (2025-03-23) 🔄 Update Updated README.md (#2501) Co-authored-by: github-actions[bot] (41e0de5) - (github-actions[bot]) Updated README.md (#2499) Co-authored-by: github-actions[bot] (9457878) - (github-actions[bot]) 📚 Documentation ... (truncated) Commits d52d20f chore(deps-dev): bump @types/node from 22.15.26 to 24.0.1 (#2587) f1c0eb9 chore(deps-dev): bump eslint-plugin-prettier from 5.4.0 to 5.4.1 (#2578) 944a0f7 chore(deps-dev): bump eslint-plugin-jest from 28.13.0 to 28.13.3 (#2585) 3dbc1e1 Updated README.md (#2592) 7a7221b chore(deps): bump github/codeql-action from 3.28.18 to 3.29.0 (#2588) c260d49 feat: add any_added to outputs (#2567) b1ccff8 Updated README.md (#2591) a892f50 docs: update link to glob patterns (#2590) 5ca5422 chore(deps-dev): bump ts-jest from 29.3.4 to 29.4.0 (#2589) See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Description There is a drawback to configuring audio routing using asound.state. Although you can specify the device of the axg-sound card via commands to output sound to either HDMI or the internal speaker, in a desktop environment, there is only one analog output (defaulting to HDMI). This is because the device actually has only one sound card. By using ALSA UCM to manage sound instances and audio routing, you can freely choose between HDMI or the built-in speaker output in a desktop environment. This is because PipeWire/WirePlumber will parse ALSA UCM and create sinks. How Has This Been Tested? build image boot form usb drive test sound in CLI and DE 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 initial support for board Luckfox Nova W. Luckfox Nova W is recently produced board on SoC Rockchip RK3308B: 4 x Cortex-A35 CPU, 512 RAM, 8 GB eMMC. It also has Ethernet, WIFI & BT, USB-A and USB-C ports, soldered microphone. Product page: https://www.luckfox.com/Luckfox-Nova?ci=646 But beware: it is very fresh board, has almost no documentation and only buildroot SDK with kernel 5.10 is available from vendor. Documentation I decided to create separate directory for vendor kernel patches. This kernel must be the same as rk35xx-vendor-6.1, but this SoC is not RK35XX. Used U-Boot is mainline. Instead of DKMS AIC8800 driver I enabled the one from kernel sources, because I needed to apply patches to it. And image builds faster than with DKMS. UART4 is used for serial console and by proprietary firmware blobs. How Has This Been Tested? [ ] eMMC does not work in mainline kernel, current and edge [x] Boot Noble 24.04 with vendor kernel rk6.1 [x] USB host and peripheral is working [x] WIFI is working [x] SPI May have quirks, though spidev-test appears to be working [ ] SPI1-M1 MISO is not receiving data [x] SPI2 is working 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 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. TI maintains its own repository of debian packages here. This PR adds this repository in TI images by-default through a new extension. So when the user performs apt update, apt install etc in Armbian images for TI boards, even TI's packages can be installed. Further, the PR also installs a few of TI's packages by-default in its images. Additionally: it also changes TI's U-boot link from git.ti.com to Github. 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. This has been tested on SK-AM62B trixie image: [ ] boot test [ ] apt update and apt install tests 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 View the full article

Description As per title How Has This Been Tested? [ ] hasn't 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This is a draft/wip for adding https proxy caching. This is especially designed for machines hosting lots of github runners to reduce their bandwidth usage by sacrificing disk space. http caching has been merged already and only needed minor changes. Caching https however is way more complicated. Encryption needs to be broken and rewrapped and then obviously downloads will fail due to cert issues. Classic MITM. So a new certificate authority (CA) needs to be put in place to allow these "fake" certs. Why is this even necessary? Well one major part is downloads from upstream apt repositories. The other major part is downloading 3rd party repositories and artifacts from OCI/ORAS/whatever the correct name for that system is. They do not allow plain http downloads but redirect to https. So in order to cache these encryption must be broken on the fly. On custom runs this works already with the mentioned extension. However when the build framework is used within a GH Actions Runner environment it would need to detect this and enable the extension automatically. No clue how to do that or overall if it is worth diving even deeper into this topic. Therefore this RFC to collect feedback. Also lots of fail-safe checks are missing. Sometimes I had to mix run_host_command_logged and chroot_sdcard since pipes don't work using latter. Documentation summary for feature / change Yes, this would need documentation. How Has This Been Tested? [x] custom builds with ENABLE_EXTENSION [ ] Test B Checklist: [no idea] 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 View the full article

Description as per title How Has This Been Tested? [x] build [ ] nope, no hw on hand right now 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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article