mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-17 18:54:42 +08:00
d0172b89b6c704679786b3a83c3ea36c148be62e
Update firmware for Intel qat_4xxx devices. This firmware is taken from Intel QuickAssist Technology Hardware Version 2.0 package QAT20.L.1.0.50-00003 [1]. Release notes for this firmware are reported at [2]. $ sha256sum qat_4xxx.bin 893caab5ce46e590c89e1dc434a28cd24a4b2405c2e63ddde6185223a3d53fba qat_4xxx.bin Link: https://downloadmirror.intel.com/783270/QAT20.L.1.0.50-00003.tar.gz [1] Link: https://intel.github.io/quickassist/RN/In-Tree/index.html [2] Signed-off-by: Adam Guerin <adam.guerin@intel.com> Signed-off-by: Gavin Troy <gavin.troy@intel.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Linux firmware
==============
<http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
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.
To submit firmware to this repository, please send either a git binary
diff or preferably a git pull request to:
linux-firmware@kernel.org
and also cc: to related mailing lists.
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 ('See LICENSE.foo for details.').
And if it were possible, a changelog of the firmware itself.
Run 'make check' to check that WHENCE is consistent with the
repository contents.
Ideally, your commit should 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).
WARNING:
=======
Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
request. Otherwise your firmware _will never be accepted_.
Maintainers are really busy, so don't expect a prompt reply.
Description
Languages
TL-Verilog
67.4%
C
23.8%
Assembly
5.4%
CMake
1.2%
Python
0.9%
Other
1.3%