No Description

Shenglei Zhang 492a1db0b8 NetworkPkg: Add Dpc protocol 4 years ago
ArmPkg 3d34b5f326 ArmPkg: DebugPeCoffExtraActionLib: fix trivial comment typos 4 years ago
ArmPlatformPkg 2a0168c7c0 ArmPlatformPkg: list module-internal header files in INF [Sources] 4 years ago
ArmVirtPkg ffe048a080 ArmVirtPkg: handle NETWORK_TLS_ENABLE in ArmVirtQemu* 5 years ago
BaseTools caa7d3a896 BaseTools/Scripts: Add GetUtcDateTime script. 4 years ago
Conf 7d83e9e847 BaseTools:Delete FrameworkDatabase from BaseTools/Conf 5 years ago
CryptoPkg 5ab96088ae CryptoPkg/OpensslLib: remove clone commands 4 years ago
DynamicTablesPkg 470626624f DynamicTablesPkg: Disable deprecated APIs 5 years ago
EmbeddedPkg f6f1e0b7c2 EmbeddedPkg: list module-internal header files in INF [Sources] 4 years ago
EmulatorPkg 538d8aaaf3 EmulatorPkg/Unix/Host: Fix XCODE5 IA32/X64 build failure 4 years ago
FatPkg 20af3a7a3e FatPkg/FatPei: Remove BootInRecoveryMode PPI DEPEX. 5 years ago
FmpDevicePkg 1f06aa24c2 FmpDEvicePkg/FmpDeviceLibNull: Implement new APIs 4 years ago
IntelFsp2Pkg c3eefcb152 IntelFsp2Pkg/FspSecCore: Add missing header file in INF file 4 years ago
IntelFsp2WrapperPkg 9ed8c3a806 IntelFsp2WrapperPkg/FspWrapperNotifyDxe: make global variable static 5 years ago
MdeModulePkg f5892aa8d8 MdeModulePkg/DxeCapsuleLibFmp: Improve comparisons in CapsuleOnDisk.c 4 years ago
MdePkg c0e174bd5b MdePkg/BaseUefiDecompressLib: Add missing description for parameter 4 years ago
NetworkPkg 492a1db0b8 NetworkPkg: Add Dpc protocol 4 years ago
OvmfPkg 1ab7d72651 OvmfPkg/PlatformPei: Change referenced MSR name. 4 years ago
PcAtChipsetPkg c78008b4b2 PcAtChipsetPkg: Remove framework modules 5 years ago
SecurityPkg e18d1c37e8 SecurityPkg/SecurityPkg.dec: Remove trailing white space 4 years ago
ShellPkg c0996b76c1 ShellPkg/UefiShellAcpiViewCommandLib: Remove the variable "Index" 4 years ago
SignedCapsulePkg 21d9dc21f8 SignedCapsulePkg: Update Package DSC to remove unused network libs 5 years ago
SourceLevelDebugPkg 4053587347 SourceLevelDebugPkg DebugCommLibUsb3: Address NULL ptr dereference case 4 years ago
StandaloneMmPkg 86094561f6 StandaloneMmPkg: Replace BSD License with BSD+Patent License 5 years ago
UefiCpuPkg 073f2cede8 UefiCpuPkg/PiSmmCpuDxeSmm: Fix coding style 4 years ago
UefiPayloadPkg 719a684d7d UefiPayloadPkg: Remove legacy PIC 8259 driver 5 years ago
.gitignore 112f4ada2e edk2: Add .DS_Store to .gitignore for macOS 7 years ago
.gitmodules 85af0b8116 ArmPkg: import Berkeley Softfloat library as git submodule 5 years ago
License-History.txt f53de8aecb edk2: Add License-History.txt 5 years ago
License.txt 304bff7223 edk2: Change License.txt from 2-Clause BSD to BSD+Patent 5 years ago
Maintainers.txt 296c908c69 Maintainers.txt: Fine-grained review ownership for MdeModulePkg 4 years ago
Readme.md 2556350d1b Readme.md: add submodule policy and clone commands 4 years ago
edksetup.bat 6759212fa6 Edk2Setup: Support different VS tool chain setup 5 years ago
edksetup.sh cf2d8d4978 edksetup.sh: remove redundant -?, -h and --help in options parsing 4 years ago

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.

Submodules

Submodule in EDK II is allowed but submodule chain should be avoided as possible as we can. Currently EDK II contains two submodules

  • CryptoPkg/Library/OpensslLib/openssl
  • ArmPkg/Library/ArmSoftFloatLib/berkeley-softfloat-3

The latter one is actually required by previous one. It’s inevitable in openssl-1.1.1 (since stable201905) for floating point parameter conversion, but should be dropped once there’s no such need in future release of openssl.

To get a full, buildable EDK II repository, use following steps of git command

$ git clone https://github.com/tianocore/edk2.git
$ cd edk2
$ git submodule update --init
$ cd ..

If there’s update for submodules, use following git commands to get the latest submodules code.

$ cd edk2
$ git pull
$ git submodule update

Note: When cloning submodule repos, ‘–recursive’ option is not recommended. EDK II itself will not use any code/feature from submodules in above submodules. So using ‘–recursive’ adds a dependency on being able to reach servers we do not actually want any code from, as well as needlessly downloading code we will not use.