mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2026-01-11 13:22:47 +08:00
52e961830b
This commit will add required Bluetooth firmware files for QCA6698 The image version is 2.1.2-00035. The QCA6698 Bluetooth chip, while sharing the same IP core as the WCN6855, has different RF components and RAM sizes. This means it requires new firmware files. Use a different firmware directory to save the NVM and rampatch files. Currently there are two connectivity boards using QCA6698 for sa8775p-ride platform, the board id are 206 and 207 respectively. So add two board specific nvm files. hpbtfw21.tlv : RAM FW dump hpnv21.b206 : NVM dump hpnv21.b207 : NVM dump hpnv21.bin : NVM dump Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.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.