暫無描述

Rebecca Cran 8fed4e47d9 OvmfPkg/build.sh: use newer '-drive if=pflash' syntax when running qemu 4 年之前
ArmPkg 4cef711d63 ArmPkg: list module-internal header files in INF [Sources] 4 年之前
ArmPlatformPkg 2a0168c7c0 ArmPlatformPkg: list module-internal header files in INF [Sources] 4 年之前
ArmVirtPkg ffe048a080 ArmVirtPkg: handle NETWORK_TLS_ENABLE in ArmVirtQemu* 5 年之前
BaseTools 959791dd6c BaseTools: Sort file list in Makefile 4 年之前
Conf 7d83e9e847 BaseTools:Delete FrameworkDatabase from BaseTools/Conf 5 年之前
CryptoPkg 9e55ce6b75 CryptoPkg/BaseCryptLib: list module-internal header files in INF [Sources] 4 年之前
DynamicTablesPkg 470626624f DynamicTablesPkg: Disable deprecated APIs 5 年之前
EmbeddedPkg f6f1e0b7c2 EmbeddedPkg: list module-internal header files in INF [Sources] 4 年之前
EmulatorPkg 70565e6422 EmulatorPkg/Unix: Convert timezone from seconds to minutes 4 年之前
FatPkg 20af3a7a3e FatPkg/FatPei: Remove BootInRecoveryMode PPI DEPEX. 5 年之前
FmpDevicePkg 43622317c6 FmpDevicePkg: Fix various typos 4 年之前
IntelFsp2Pkg 520a1e60de IntelFsp2Pkg: PeiService pointer not reset to 0 in SecMain 4 年之前
IntelFsp2WrapperPkg 9ed8c3a806 IntelFsp2WrapperPkg/FspWrapperNotifyDxe: make global variable static 5 年之前
MdeModulePkg 034a3b4f55 MdeModulePkg/Setup: Check ConfigAccess protocol in case it's destroyed 5 年之前
MdePkg 28bc699240 MdePkg/UefiDebugLibStdErr: Add destructor to CloseEvent 4 年之前
NetworkPkg 07135c1220 NetworkPkg: Move Network library header file from MdeModulePkg to NetworkPkg 5 年之前
OvmfPkg 8fed4e47d9 OvmfPkg/build.sh: use newer '-drive if=pflash' syntax when running qemu 4 年之前
PcAtChipsetPkg c78008b4b2 PcAtChipsetPkg: Remove framework modules 5 年之前
SecurityPkg c027f68030 SecurityPkg: set SM3 bit in TPM 2.0 hash mask by default 4 年之前
ShellPkg 8ff68cd5e4 ShellPkg: acpiview: DBG2: Remove redundant forward declarations 4 年之前
SignedCapsulePkg 21d9dc21f8 SignedCapsulePkg: Update Package DSC to remove unused network libs 5 年之前
SourceLevelDebugPkg 34857c2ff9 SourceLevelDebugPkg: Add missing instances for build only 5 年之前
StandaloneMmPkg 86094561f6 StandaloneMmPkg: Replace BSD License with BSD+Patent License 5 年之前
UefiCpuPkg 87ad6913b4 UefiCpuPkg/RegisterCpuFeaturesLib: Start all processors simultaneously. 4 年之前
UefiPayloadPkg 719a684d7d UefiPayloadPkg: Remove legacy PIC 8259 driver 5 年之前
.gitignore 112f4ada2e edk2: Add .DS_Store to .gitignore for macOS 7 年之前
.gitmodules 85af0b8116 ArmPkg: import Berkeley Softfloat library as git submodule 5 年之前
License-History.txt f53de8aecb edk2: Add License-History.txt 5 年之前
License.txt 304bff7223 edk2: Change License.txt from 2-Clause BSD to BSD+Patent 5 年之前
Maintainers.txt 296c908c69 Maintainers.txt: Fine-grained review ownership for MdeModulePkg 4 年之前
Readme.md b8993a34ae edk2: Update additional licenses in Readme.md 5 年之前
edksetup.bat 6759212fa6 Edk2Setup: Support different VS tool chain setup 5 年之前
edksetup.sh cf2d8d4978 edksetup.sh: remove redundant -?, -h and --help in options parsing 4 年之前

Readme.md

EDK II Project

A modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications from www.uefi.org.

The majority of the content in the EDK II open source project uses a BSD-2-Clause Plus Patent License. The EDK II open source project contains the following components that are covered by additional licenses:

The EDK II Project is composed of packages. The maintainers for each package are listed in Maintainers.txt.

Resources

Code Contributions

To make a contribution to a TianoCore project, follow these steps.

  1. Create a change description in the format specified below to use in the source control commit log.
  2. Your commit message must include your Signed-off-by signature
  3. Submit your code to the TianoCore project using the process that the project documents on its web page. If the process is not documented, then submit the code on development email list for the project.
  4. It is preferred that contributions are submitted using the same copyright license as the base project. When that is not possible, then contributions using the following licenses can be accepted:

For documentation:

Contributions of code put into the public domain can also be accepted.

Contributions using other licenses might be accepted, but further review will be required.

Developer Certificate of Origin

Your change description should use the standard format for a commit message, and must include your Signed-off-by signature.

In order to keep track of who did what, all patches contributed must include a statement that to the best of the contributor’s knowledge they have the right to contribute it under the specified license.

The test for this is as specified in the Developer’s Certificate of Origin (DCO) 1.1. The contributor certifies compliance by adding a line saying

Signed-off-by: Developer Name developer@example.org

where Developer Name is the contributor’s real name, and the email address is one the developer is reachable through at the time of contributing.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Sample Change Description / Commit Message

From: Contributor Name <contributor@example.com>
Subject: [Repository/Branch PATCH] Pkg-Module: Brief-single-line-summary

Full-commit-message

Signed-off-by: Contributor Name <contributor@example.com>

Notes for sample patch email

  • The first line of commit message is taken from the email’s subject line following [Repository/Branch PATCH]. The remaining portion of the commit message is the email’s content.
  • git format-patch is one way to create this format

Definitions for sample patch email

  • Repository is the identifier of the repository the patch applies. This identifier should only be provided for repositories other than edk2. For example edk2-BuildSpecification or staging.
  • Branch is the identifier of the branch the patch applies. This identifier should only be provided for branches other than edk2/master. For example edk2/UDK2015, edk2-BuildSpecification/release/1.27, or staging/edk2-test.
  • Module is a short identifier for the affected code or documentation. For example MdePkg, MdeModulePkg/UsbBusDxe, Introduction, or EDK II INF File Format.
  • Brief-single-line-summary is a short summary of the change.
  • The entire first line should be less than ~70 characters.
  • Full-commit-message a verbose multiple line comment describing the change. Each line should be less than ~70 characters.
  • Signed-off-by is the contributor’s signature identifying them by their real/legal name and their email address.