RSS Bot

The latest 6.11 kernel release is here! This release improves performance, security, and hardware compatibility, increasing the kernel's flexibility and efficiency for various computing environments. View the full article

It is now possible to start kicking the tires on Vulkan with an open source driver on Arm Mali-G610 and Mali-G310 GPUs. The Panfrost project continues to grow! View the full article

X96Q LPDDR3 Improvements 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. Improvements include EMMC detection Bluetooth LED functionality USB functionality Now boots on edge Miniarch had a much better setup for X96Q than my original, so used those dts files with minimal changes. View the full article

Description When m.2 wifi module has a usb bluetooth, it can get detected but has error when loading driver: rejected 1 configuration due to insufficient available bus power This commit will add a udev rule setting all usb device attr bConfigurationValue to 1 if it has a null value, which will fix the bluetooth usb device. Hint from https://community.nxp.com/t5/i-MX-Processors/USB-1-0-disable-100mA-current-limit-permanently/td-p/1600252 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 BOARD=armsom-w3 BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base ENABLE_EXTENSIONS="mesa-vpu" 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 Bump edge kernel to 6.11 for rockchip 32 bit family. Notably: several driver have the .remove hook which is now void in place of int (upstream kernel devs changed this) the patch to compile the device tree overlays (actually, it is for the .scr files) has been adapted because of minor changes from 6.10 GitHub issue reference: Jira reference number AR-2494 How Has This Been Tested? [x] Kernel built successfully [x] Kernel testedon a live rk322x board [x] Kernel tested on a live rk3288 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 View the full article

rockchip-rk3588/6.11: backport Marcin Juszkiewicz's "FriendlyELEC NanoPC-T6 improvements" v6 series to fix non-LTS and split LTS version of NanoPC T6 nanopct6-lts: a separate board for the LTS version of the NanoPC T6 Split has landed upstream for 6.12, and backported in a separate commit I had already added the -lts version to the vendor (6.1) rockchip kernel a few months ago rockchip-rk3588/6.11: backport Marcin Juszkiewicz's "FriendlyELEC NanoPC-T6 improvements" v6 series to fix non-LTS and split LTS version of NanoPC T6 Marcin Juszkiewicz's series https://lore.kernel.org/all/20240829-friendlyelec-nanopc-t6-lts-v6-0-edff247e8c02@linaro.org/ has landed upstream see https://github.com/torvalds/linux/commit/db1dcbe5f752d423421f77d54d246398b196f670 thus we have 2 separate DTs, one for non-LTS, one for LTS; thus also 2 different Armbian boards (see separate commit) drop my own patch that added SPI NOR to the T6, as that is now included in the base DT this patch shall be dropped when 6.12-rc1 is released View the full article

patching: emit warnings when files in dt folder overwrite pre-existing files (DTs that landed upstream) patching: emit warnings when files in dt folder overwrite pre-existing files (DTs that landed upstream) it's more and more common that the (bare) DT files in our dt folders have landed upstream this adds warnings and marks the patching table red when some bare-dt file overwrites what's already in git without this it's very easy to forget them there during bumps View the full article

Bumps setuptools from 74.1.0 to 75.1.0. Changelog Sourced from setuptools's changelog. v75.1.0 Features Deprecated bdist_wheel.universal configuration. (#4617) Bugfixes Removed reference to upload_docs module in entry points. (#4650) v75.0.0 Features Declare also the dependencies used by distutils (adds jaraco.collections). Deprecations and Removals Removed upload_docs command. (#2971) pypa/distutils#294#4649) v74.1.3 Bugfixes Fix cross-platform compilation using distutils._msvccompiler.MSVCCompiler -- by :user:saschanaz and :user:Avasam (#4648) v74.1.2 Bugfixes Fixed TypeError in sdist filelist processing by adding support for pathlib Paths for the build_base. (#4615) Removed degraded and deprecated test_integration (easy_install) from the test suite. (#4632) ... (truncated) Commits 3106af0 Bump version: 75.0.0 → 75.1.0 37c3d27 Removed reference to upload_docs module in entry points. 9fb53fd Merge pull request #4617 from abravalheri/issue-4612 cd3ba7d Merge pull request #4644 from DimitriPapadopoulos/codespell 5e27b2a Bump version: 74.1.3 → 75.0.0 af9e245 Merge pull request #4649 from pypa/feature/distutils-7283751 f15861e Add news fragment. ce01828 Merge https://github.com/pypa/distutils into feature/distutils-7283751 378984e Remove news fragments, not useful here. ffdf0bd Merge tag 'v74.1.3' 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 dtschema from 2024.5 to 2024.9. Commits c51125d schemas: i2c: add generic interrupt name for I2C controllers 285f991 schemas: i2c: clean up interrupt descriptions for I2C targets 74bc7ea schemas: i2c: reword descriptions for inclusive language 5270b95 dt-validate: Support multiple schema id matches 449b457 schemas: property-units: Exclude some non-conforming properties 8f5303c meta-schemas: Disable checks on non-conformant unit suffix properties e5d88ac dtb: Fix 'interrupt-map' decoding for single entry 69c4839 validator: Decend allOf/anyOf/oneOf keywords when extracting properties f13c181 dtb: Handle multiple types differing in sign c00f747 dtb: Handle multiple types for 'dma-masters' 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.1.30 to 0.2.2. Release notes Sourced from oras's releases. Oras Python Release v0.2.2 What's Changed Token Auth Backend: Token request function didn`t set Authorization Header by @mariusbertram in oras-project/oras-py#153 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.1...0.2.2 Oras Python Release v0.2.1 What's Changed wip: separate auth into backends by @vsoch in oras-project/oras-py#134 docs: use valid media_type format in examples by @tarilabs in oras-project/oras-py#139 [tributors] contributors/update-2024-06-06 by @github-actions in oras-project/oras-py#140 chore: fix typing for manifest_config param of push fn by @tarilabs in oras-project/oras-py#141 core: make push response the one pertaining to Manifest (not config by @tarilabs in oras-project/oras-py#146 fix(core): provider do_request to maintain verify in all request, basic headers by @tarilabs in oras-project/oras-py#145 Enable chunked uploads by @isinyaaa in oras-project/oras-py#150 [tributors] contributors/update-2024-09-04 by @github-actions in oras-project/oras-py#151 New Contributors @tarilabs made their first contribution in oras-project/oras-py#139 @isinyaaa made their first contribution in oras-project/oras-py#150 Full Changelog: https://github.com/oras-project/oras-py/compare/0.1.30...0.2.1 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) 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 patch fix for proper validation and specification of the subject element add tls_verify to provider class for optional disable tls verification (0.1.22) Allow to pull exactly to PWD (0.1.21) Ensure insecure is passed to provider class (0.1.20) patch fix for blob upload Windows, closes issue 93 (0.1.19) patch fix for empty manifest config on Windows, closes issue 90 (0.1.18) patch fix to correct session url pattern, closes issue 78 (0.1.17) add support for tag deletion and retry decorators (0.1.16) bugfix that pagination sets upper limit of 10K (0.1.15) pagination for tags (and general function for pagination) (0.1.14) expose upload_blob function to be consistent (0.1.13) ensure we always strip path separators before pull/push (0.1.12) exposing download_blob to the user since it uses streaming (0.1.11) adding developer examples for pull. start deprecation for _download_blob, _put_upload, _chunked_upload, _upload_manifest in favor of equivalent public functions. moving of docs to fully be here with extended examples (0.1.1) addition of oras.utils.workdir to provide local context clients are removed from Python SDK in favor of examples (0.1.0) login refactored to be part of the basic client ... (truncated) Commits 5d7b80d Token Auth Backend: Token request function didn`t set Authorization Header (#... 5763015 Automated deployment to update contributors 2024-09-04 (#151) dfc2415 Enable chunked uploads (#150) caf8db5 fix(core): provider do_request to maintain verify in all request, basic heade... b8c4885 core: make push response the one pertaining to Manifest (not config (#146) fd8a83c Merge pull request #141 from tarilabs/tarilabs-20240606-manifest_config 3a571e3 chore: fix typing for manifest_config param of push fn 9527aa1 Merge pull request #140 from oras-project/contributors/update-2024-06-06 19c1cb5 Automated deployment to update contributors 2024-06-06 571a23f Merge pull request #139 from tarilabs/tarilabs-20240605-docMediaType 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

Description display armbian-install command only up to one day and if armbian-install was not run yet. hide displaying BASH shell at first login when this is the only option (minimal images). De-clutter 1st login screen. add variable INSTALLED=true to /etc/armbian-image-release indicating armbian-install was executed. How Has This Been Tested? Manual run. 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 This pull requests adds a device tree overlay for the Odroid C4 enabling hardware SPI on pins 19, 21, 23 and 24 on the GPIO header. It doesn't require any other changes, except one additional line in the Makefile. Besides, it can replace the old device tree meson-sm1-odroid-c4-spidev.dtb (which activates wrong pins and doesn't work due to this) while offering more flexibility. How Has This Been Tested? The SPI communication has been successfully tested with a LogicPort analyzer and some custom made FPGA board (SPI readout of a Mamamatsu silicon spectrometer). [x] Logic Analyzer: timing of MOSI vs. SCK has been verified, maximum speed is about 12MHz for SCK [x] data transfer between C4 and spectrometer FPGA has been tested 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

Collabora will be in Vienna for the Media Summit, Open Source Summit Europe, and Linux Plumbers! Catch one of our many talks. View the full article

Description add patch which add to vendor u-boot support for sata boot from m.2 e-key(switch m.2 to sata and extra sata defconfig) added additional u-boot target too build the additional u-boot image with these changes the patch can be removed if this pull request for vendor u-boot for rock-3a is accepted https://github.com/radxa/u-boot/pull/95 Documentation summary for feature / change rock-3a:add u-boot image for sata boot on m.2 e.key for sata boot the rkspi_loader_sata.img has to be flashed on spi flash (use dd or flashcp) flash armbian image to sata device with dd (or ifd3f/caligula , etcher cli ) mount armbian boot partition on sata device and add rock-3a-sata too useroverlay poweroff and remove sdcard( or emmc ) to boot from sata armbian install doesnt work because u-boot needs extra vfat boot partition which armbian install doesnt create only single partition How Has This Been Tested? compiled with github ci https://github.com/pykpkg47/armbian-image-build/actions/runs/10874313933/job/30171463631 compile log https://paste.armbian.com/fasuhomeri artifacts : https://github.com/pykpkg47/armbian-image-build/releases/tag/24.8.3 tested on rock-3a u-boots detects sata ssd connected via adapter to m.2 e-key and boots kernel from it 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 Proposed by mboehmer How Has This Been Tested? Not tested yet. 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 What comes out of automation - no other changes. How Has This Been Tested? Haven't been tested, CI will do this job. Checklist: [ ] 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 6.6.51. 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

As guests at the STMicroelectronics booth, Collabora will be demonstrating how the STM32MP2 chip is perfectly suited for enabling edge AI solutions in industrial environments. 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 This exposes the ITC content type provided by hdmi spec to v4l2. This allows user space applications to query the driver using V4L2_CID_DV_RX_IT_CONTENT_TYPE. This way user applications can see not only if a hdmi is plugged in or not, but also what type of video is being transmitted. For my use case specifically, I just want to know if the recieved type is no type (V4L2_DV_IT_CONTENT_TYPE_NO_ITC) or literally anything else. This would let me detect when my main computer's goes to sleep with the hdmi out from the main computer plugged into the OP5+ HDMI in. Without this patch, there's no way to tell that happened, as for my gpu/hdmi plug, it keeps the hot plug detection pin high the whole time. How Has This Been Tested? tested on orange pi 5 plus Checklist: [ x] I have performed a self-review of my own code [ x] My changes generate no new warnings 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. GitHub issue reference: 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. [ ] Test A [ ] Test B 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

Description Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project View the full article

Description Minor regression fix for extensions that need to modify the root device, such as LVM and Crypto Root. Fix for newer ubuntu build host requiring re-instantiation of LVM devices mid build process. GitHub issue reference: #7210 Jira reference number AR-2489 How Has This Been Tested? The build process failed before, now builds again. Tested with Jammy and Noble, installed distributions, etc. View the full article

Description Context systemd's cloud-init.target and armbian-firstrun.service will be started concurrently (both are wanted by multi-user.target). Both will try to create SSH host keys by default: armbian-firstrun will always delete SSH host keys and then generate new ones cloud-init.target (by default) will always delete SSH host keys and then generate new ones. Problem When one must run armbian-firstrun and cloud-init, there is no deterministic ordering between the 2 files execution and therefore no one can guarantee which will be last to setup OpenSSH host keys. In my current scenario, host keys are explicitly setup in cloud-init and I would expect armbian-firstrun to not delete keys + no ssh host key generation. Implemented Solution armbian-firstrun support user defined config to optionally regenerate SSH host keys: no: no ssh key deleted + no ssh host key generated. Allow cloud-init to take over this behaviour deterministically. yes (or undefined): ssh host key deleted + generated (compatibility: current armbian behaviour) Documentation summary for feature / change 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: [x] short description armbian-firstrun: Optionally skip OpenSSH host key regeneration [x] summary To skip armbian-firstrun's OpenSSH host key deletion + regeneration (eg: to let cloud-init set the SSH host keys), then define OPENSSHD_REGENERATE_HOST_KEYS=no in the /path/to/userpatches/config-*.conf file used by ./compile.sh to build the image. [ ] example of usage See above How Has This Been Tested? [ ] qemu-x86 board: build with OPENSSHD_REGENERATE_HOST_KEYS=no and expect armbian-firstrun to not regenerate ssh host keys [ ] [Test B](qemu-x86 board: build without OPENSSHD_REGENERATE_HOST_KEYS set and expect armbian-firstrun to regenerate ssh host keys 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 View the full article

Description HDMI-rx does not properly report if it is plugged out and says that it is plugged in all the time. The cause is the following. There is an irq that is watching a gpio for 5v high. During the plugout method for the driver, the driver resets the device state. If the irq that is watching for gpio 5 volts is not disabled during this time, it triggers on a transient voltage and sets the driver to run the "High"/plugged in logic. By the time the driver reaches the high logic, the gpio is low again, which resets the cycle by re-calling the plugout method. This is probably why @efectn disabled the log in 0a0eb46 , because it's so noisy and spams the logs. I don't know if this is the right solution, but I know it prevents this cycle by disabling the irq during the plugout code sequence. How Has This Been Tested? Tested on orange pi 5 plus Checklist: Please delete options that are not relevant. [ x ] My changes generate no new warnings View the full article