Merge branch 'robot/pr-0-1781081510' into 'main' robot/pr-0-1781081510 See merge request kernel-firmware/linux-firmware!1091
This repository contains all these firmware images which have been extracted from older drivers, as well various new firmware images which we were never permitted to include in a GPL'd work, but which we have been permitted to redistribute under separate cover.
The upstream repository is located at https://gitlab.com/kernel-firmware/linux-firmware.git.
To submit firmware to this repository, please do one of the following:
linux-firmware@kernel.orglinux-firmware@kernel.orgAll commits must include a Signed-off-by line to track the provenance of the firmware. This signature must be from someone with authority over the licensing of the firmware, typically someone from within the company that owns or controls the firmware. The Signed-off-by line serves as an attestation that the contributor has the right to submit the firmware under the specified license terms and that it can be redistributed according to those terms.
At times, a contributor may work at a location that makes it difficult to submit patches or MRs from their offical company accounts. In this case, the Signed-off-by line in the commit should still be via the company address, but the submitter can use a personal address with the company address on CC for the MR or patch contribution.
AI assisted contributions are welcome. If a commit was aided by or generated by an AI agent or tool, the contribution must note this in the commit message using an Assisted-by: trailer (or a similar convention such as Co-developed-by:), naming the tool or model used. The exact tag is not critical; clearly surfacing that AI was involved in producing the change is what matters. This requirement is in addition to, and does not replace, the Signed-off-by requirement above.
If your commit adds new firmware, it must update the WHENCE file to clearly state the license under which the firmware is available, and that it is redistributable. Being redistributable includes ensuring the firmware license provided includes an implicit or explicit patent grant to end users to ensure full functionality of device operation with the firmware. If the license is long and involved, the license text may be kept in a separate file rather than inline in WHENCE. Any such separate license file must be placed in the LICENSES/ directory and referenced from the WHENCE file (IE ‘See LICENSE.foo for details.’).
Where possible, the commit message should also include a changelog of the firmware itself — what changed in this revision — since for binary firmware the commit message is frequently the only human-readable record of the change.
To maintain consistent quality on the repository, please run the following before submitting a patch:
make check
If you don't have pre-commit installed, you can install it with:
pip install pre-commit
Your commit must contain a Signed-Off-By: from someone authoritative on the licensing of the firmware in question (i.e. from within the company that owns the code).
CONFIDENTIALITY STATEMENT in your e-mail, patch or request. Otherwise your firmware will never be accepted.