mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-17 18:54:42 +08:00
8a507494f3
Using link-to-a-link reduces legibility and changes to the root link, also changes the leafs. Where the latter may be undesired and in some cases just wrong. We have a couple of instances in-tree, so fix them up and ban the combination. One particularly good example, why we'd want this is: https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/272 In there we have the following: File: ti/tas2781/TAS2XXX1EB30.bin [snip] Link: TAS2XXX1EB3.bin -> ti/tas2781/TAS2XXX1EB3.bin Link: ti/tas2781/TAS2XXX1EB3.bin -> TAS2XXX1EB30.bin Link: TAS2XXX1EB30.bin -> ti/tas2781/TAS2XXX1EB30.bin Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Linux firmware
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.
Submitting firmware
To submit firmware to this repository, please do one of the following:
- open a MR upstream
- send a git binary diff to
linux-firmware@kernel.org - send a git pull request to:
linux-firmware@kernel.org
Quality
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).
Warnings
- Don't send any
CONFIDENTIALITY STATEMENTin your e-mail, patch or request. Otherwise your firmware will never be accepted. - Maintainers are really busy, so don't expect a prompt reply.