Move firmware licenses to a LICENSES/ directory Move the top-level firmware license texts, and the few that are not at the top level[1], to a LICENSES/ directory, as per the FSFE's REUSE specification[2]. This tidies up the top level of the source tree, consolidates the texts, and is a small step towards fully automated license scanning using SPDX tags. Update check_whence.py so that the WHENCE can still just refer to the filename and LICENSES/ is prepended automatically. [1] qca/NOTICE.txt, qcom/NOTICE.txt, wfx/LICENCE.wf200 [2] https://reuse.software Signed-off-by: Ross Burton <ross.burton@arm.com>
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.
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, it's permitted to include it in a separate file and refer to it from the WHENCE file (IE ‘See LICENSE.foo for details.’). And if it were possible, a changelog of the firmware itself.
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.