public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Abner Chang" <abner.chang@hpe.com>
To: devel@edk2.groups.io
Cc: abner.chang@hpe.com, Bret Barkelew <Bret.Barkelew@microsoft.com>,
	Sean Brogan <sean.brogan@microsoft.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	Gilbert Chen <gilbert.chen@hpe.com>,
	Daniel Schaefer <daniel.schaefer@hpe.com>
Subject: [edk2/master PATCH RISC-V CI v2 0/5] RISC-V EDK2 CI configuration files.
Date: Mon,  9 Mar 2020 17:53:13 +0800	[thread overview]
Message-ID: <20200309095318.7331-1-abner.chang@hpe.com> (raw)

Address Sean's comments on "edk2/master PATCH RISC-V CI v1".
- Remove dependency of RiscVPkg from MdeModulePkg.ci.yaml.
- Add SHA to gcc_riscv64_unknown_ext_dep.yaml
- Create empty ExtendWords in both RiscVPkg.ci.yaml and RiscVPlatformPkg.ci.yaml.

BZ:2562:
https://bugzilla.tianocore.org/show_bug.cgi?id=2562

This set of patches enale RISC-V architecture on EDK2 CI test process.
The external dependency of toolchain for RISCV64 architecture is retrieved from:
https://media.githubusercontent.com/media/riscv/riscv-uefi-edk2-docs/master/gcc-riscv-edk2-ci-toolchain/.

Signed-off-by: Abner Chang <abner.chang@hpe.com>

Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Gilbert Chen <gilbert.chen@hpe.com>
Cc: Daniel Schaefer <daniel.schaefer@hpe.com>

Abner Chang (5):
  RiscVPlatformPkg: Add RiscVPlatformPkg yaml file for EDK2 CI.
  RiscVPkg: Add RiscVPkg yaml file for EDK2 CI.
  BaseTools: Enable RISC-V architecture for RISC-V EDK2 CI.
  .azurepipelines: Add RISC-V architecture on RISC-V EDK2 CI.
  .pytool: Add RISC-V architecture on RISC-V EDK2 CI.

 .azurepipelines/Ubuntu-GCC5.yml               |  3 +-
 .pytool/CISettings.py                         | 15 +++-
 .../Bin/gcc_riscv64_unknown_ext_dep.yaml      | 22 ++++++
 .../LinuxGcc5ToolChain/LinuxGcc5ToolChain.py  | 31 +++++++++
 RiscVPkg/RiscVPkg.ci.yaml                     | 68 ++++++++++++++++++
 RiscVPlatformPkg/RiscVPlatformPkg.ci.yaml     | 69 +++++++++++++++++++
 6 files changed, 204 insertions(+), 4 deletions(-)
 create mode 100644 BaseTools/Bin/gcc_riscv64_unknown_ext_dep.yaml
 create mode 100644 RiscVPkg/RiscVPkg.ci.yaml
 create mode 100644 RiscVPlatformPkg/RiscVPlatformPkg.ci.yaml

-- 
2.25.0


             reply	other threads:[~2020-03-09 10:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  9:53 Abner Chang [this message]
2020-03-09  9:53 ` [edk2/master PATCH RISC-V CI v2 1/5] RiscVPlatformPkg: Add RiscVPlatformPkg yaml file for EDK2 CI Abner Chang
2020-03-20  0:51   ` [edk2-devel] " Michael D Kinney
2020-03-09  9:53 ` [edk2/master PATCH RISC-V CI v2 2/5] RiscVPkg: Add RiscVPkg " Abner Chang
2020-03-20  0:51   ` [edk2-devel] " Michael D Kinney
2020-03-22  3:12     ` Abner Chang
2020-03-09  9:53 ` [edk2/master PATCH RISC-V CI v2 3/5] BaseTools: Enable RISC-V architecture for RISC-V " Abner Chang
2020-03-21  0:32   ` [edk2-devel] " Rebecca Cran
2020-03-09  9:53 ` [edk2/master PATCH RISC-V CI v2 4/5] .azurepipelines: Add RISC-V architecture on " Abner Chang
2020-03-09  9:53 ` [edk2/master PATCH RISC-V CI v2 5/5] .pytool: " Abner Chang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200309095318.7331-1-abner.chang@hpe.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox