Brak opisu

Michael D Kinney 4baa783d5e .mergify: Add Mergify YML pull request rules configuration file 4 lat temu
.azurepipelines 106c7a991c .azurepipelines: Add Azure Pipelines YML configuration files 4 lat temu
.mergify 4baa783d5e .mergify: Add Mergify YML pull request rules configuration file 4 lat temu
.pytool 4eb2baba93 .pytool: Add CISettings.py and Readme.md 4 lat temu
ArmPkg 92c8588f93 ArmPkg: strip trailing whitespace 4 lat temu
ArmPlatformPkg df8f8688b8 ArmPlatformPkg: strip trailing whitespace 4 lat temu
ArmVirtPkg 23ab8df01a ArmVirtPkg/PlatformBootManagerLib: Don't update progress if Pcd is 0 4 lat temu
BaseTools de4ce46d6e BaseTools: Add BaseTools plugins to support CI 4 lat temu
Conf 7d83e9e847 BaseTools:Delete FrameworkDatabase from BaseTools/Conf 5 lat temu
CryptoPkg f98a44541f CryptoPkg: Add YAML file for CI builds 4 lat temu
DynamicTablesPkg f413d9bee3 DynamicTablesPkg: Arm SRAT Table Generator 4 lat temu
EmbeddedPkg 601a18bf08 EmbeddedPkg/DtPlatformDxe: Add DT/ACPI Default Flexibility 4 lat temu
EmulatorPkg 2737037a41 EmulatorPkg: Enable CLANG9 tool chain 4 lat temu
FatPkg 6d807aef57 FatPkg: Add YAML file for CI builds 4 lat temu
FmpDevicePkg 8bc648fe6c FmpDevicePkg: Add YAML file for CI builds 4 lat temu
IntelFsp2Pkg 9e639c1cb6 IntelFsp2Pkg/SplitFspBin.py: Command crashed when FV almost full. 4 lat temu
IntelFsp2WrapperPkg 7bf5255997 IntelFsp2WrapperPkg: Remove unneeded MdeModulePkg dependency 4 lat temu
MdeModulePkg e4612477b9 MdeModulePkg: Add YAML file for CI builds 4 lat temu
MdePkg 3059a38d5f MdePkg: Add YAML file for CI builds 4 lat temu
NetworkPkg 420c859831 NetworkPkg: Add YAML file for CI builds 4 lat temu
OvmfPkg d511d6e0e7 OvmfPkg: Disable variable runtime cache 4 lat temu
PcAtChipsetPkg d495762a97 PcAtChipsetPkg: Add YAML files for CI builds 4 lat temu
SecurityPkg 566c45a533 SecurityPkg: Add YAML files for CI builds 4 lat temu
ShellPkg e3b8a0081b ShellPkg: Add YAML file for CI builds 4 lat temu
SignedCapsulePkg 3137900fc9 SignedCapsulePkg: Use BaseCryptLibNull to reduce package CI time 4 lat temu
SourceLevelDebugPkg 4053587347 SourceLevelDebugPkg DebugCommLibUsb3: Address NULL ptr dereference case 4 lat temu
StandaloneMmPkg 81e9eca7a4 StandaloneMmPkg/Core: Fix typo in function name 4 lat temu
UefiCpuPkg 30c00d7f19 UefiCpuPkg: Add YAML file for CI builds 4 lat temu
UefiPayloadPkg 976d0353a6 UefiPayloadPkg/BlSupportDxe: fix ReserveResourceInGcd() calls 4 lat temu
.gitignore 48760409cc .gitignore: Ignore python compiled files, extdeps, and vscode 4 lat temu
.gitmodules 85af0b8116 ArmPkg: import Berkeley Softfloat library as git submodule 5 lat temu
License-History.txt f53de8aecb edk2: Add License-History.txt 5 lat temu
License.txt 304bff7223 edk2: Change License.txt from 2-Clause BSD to BSD+Patent 5 lat temu
Maintainers.txt 021eb1820e Maintainers.txt: Add continuous integration(CI) directories 4 lat temu
Readme.md cc6854506c Readme.md: remove positional references from submodule description 4 lat temu
edksetup.bat 670c903a68 Add VS2019 Support on ToolSetup Batches 4 lat temu
edksetup.sh cf2d8d4978 edksetup.sh: remove redundant -?, -h and --help in options parsing 4 lat temu
pip-requirements.txt ab5892f260 pip-requirements.txt: Add python pip requirements file 4 lat temu

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 the following submodules

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

ArmSoftFloatLib is actually required by OpensslLib. 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.