mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-16 18:33:05 +08:00
9ee52be785
Add AMD Secure Encrypted Virtualization (SEV) firmware to allow for the updating of the SEV firmware outside of BIOS releases. Naming convention and directory structure follows the convention defined in the kernel driver in drivers/crypto/ccp/psp-dev.c SEV firmware files are to be placed in the "amd" directory and names should follow the pattern: amd_sev_fam<FAMILY>h_model<MODEL>h.sbin where FAMILY is the two-digit hexadecimal value of the target processor family (e.g. 17) where MODEL is the two-digit hexadecimal value of the target processor model (e.g. 01) or where the least significant nibble of the two-digit hexadecimal value can be an 'x' to indicate a range of models (e.g. 0x for 00 to of). The firmware provided is version 0.17 build 11 and is for AMD family 17h processors with models in the range 00h to 0fh. Signed-off-by: John Allen <john.allen@amd.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.