public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"abner.chang@hpe.com" <abner.chang@hpe.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Leif Lindholm <leif@nuviainc.com>,
	Gilbert Chen <gilbert.chen@hpe.com>,
	Daniel Schaefer <daniel.schaefer@hpe.com>
Subject: Re: [edk2-devel] [edk2/master PATCH RISC-V CI Code Changes v1 01/11] FatPkg: Add RISC-V architecture for EDK2 CI.
Date: Thu, 12 Mar 2020 05:39:41 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C492A3A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20200306053620.12131-2-abner.chang@hpe.com>

Abner,
Has the change to BaseTools supporting new ARCH been merged?

Liming, Mike,
Does INF specification need to be updated for this new ARCH?

Thanks,
Ray

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Abner Chang
> Sent: Friday, March 6, 2020 1:36 PM
> To: devel@edk2.groups.io
> Cc: abner.chang@hpe.com; Ni, Ray <ray.ni@intel.com>; Leif Lindholm <leif@nuviainc.com>; Gilbert Chen
> <gilbert.chen@hpe.com>; Daniel Schaefer <daniel.schaefer@hpe.com>
> Subject: [edk2-devel] [edk2/master PATCH RISC-V CI Code Changes v1 01/11] FatPkg: Add RISC-V architecture for EDK2 CI.
> 
> BZ:2562:
> https://bugzilla.tianocore.org/show_bug.cgi?id=2562
> 
> Add RISC-V architecture for EDK2 CI testing.
> 
> Signed-off-by: Abner Chang <abner.chang@hpe.com>
> 
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Gilbert Chen <gilbert.chen@hpe.com>
> Cc: Daniel Schaefer <daniel.schaefer@hpe.com>
> ---
>  FatPkg/FatPkg.dsc | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/FatPkg/FatPkg.dsc b/FatPkg/FatPkg.dsc
> index 1676c2eb8f..d86256068b 100644
> --- a/FatPkg/FatPkg.dsc
> +++ b/FatPkg/FatPkg.dsc
> @@ -4,6 +4,7 @@
>  #  This Platform file is used to generate the Binary Fat Drivers
> 
>  #  for EDK II Prime release.
> 
>  #  Copyright (c) 2007 - 2018, Intel Corporation. All rights reserved.<BR>
> 
> +#  Copyright (c) 2020, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
> 
>  #
> 
>  #  SPDX-License-Identifier: BSD-2-Clause-Patent
> 
>  #
> 
> @@ -14,7 +15,7 @@
>    PLATFORM_GUID                  = 25b55dbc-9d0b-4a32-80da-46e1273d622c
> 
>    PLATFORM_VERSION               = 0.3
> 
>    DSC_SPECIFICATION              = 0x00010005
> 
> -  SUPPORTED_ARCHITECTURES        = IA32|X64|EBC|ARM|AARCH64
> 
> +  SUPPORTED_ARCHITECTURES        = IA32|X64|EBC|ARM|AARCH64|RISCV64
> 
>    OUTPUT_DIRECTORY               = Build/Fat
> 
>    BUILD_TARGETS                  = DEBUG|RELEASE|NOOPT
> 
>    SKUID_IDENTIFIER               = DEFAULT
> 
> --
> 2.25.0
> 
> 
> -=-=-=-=-=-=
> Groups.io Links: You receive all messages sent to this group.
> 
> View/Reply Online (#55584): https://edk2.groups.io/g/devel/message/55584
> Mute This Topic: https://groups.io/mt/71767323/1712937
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub  [ray.ni@intel.com]
> -=-=-=-=-=-=


  reply	other threads:[~2020-03-12  5:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  5:36 [edk2/master PATCH RISC-V CI Code Changes v1 00/11] Necessary code changes for RISCV64 CI testing Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 01/11] FatPkg: Add RISC-V architecture for EDK2 CI Abner Chang
2020-03-12  5:39   ` Ni, Ray [this message]
2020-03-12  6:27     ` [edk2-devel] " Abner Chang
2020-03-12  6:47       ` Liming Gao
2020-03-20  1:16         ` Michael D Kinney
2020-03-20  3:28           ` Liming Gao
2020-03-20  3:49             ` Bob Feng
2020-03-12  7:07   ` Ni, Ray
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 02/11] FmpDevicePkg: " Abner Chang
2020-03-27  3:20   ` [edk2-devel] " Liming Gao
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 03/11] NetworkPkg: " Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 04/11] NetworkPkg/HttpBootDxe: " Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 05/11] CryptoPkg: " Abner Chang
2020-03-17  9:19   ` Xiaoyu Lu
2020-07-13  9:27   ` [edk2-devel] " Laszlo Ersek
2020-07-13 18:05     ` Laszlo Ersek
2020-07-14  1:13       ` Abner Chang
2020-07-22  0:58   ` Guomin Jiang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 06/11] MdePkg/Include: Add RISC-V related definitions " Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 07/11] SecurityPkg: Security package changes for RISC-V " Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 08/11] ShellPkg: Shell " Abner Chang
2020-03-12  2:21   ` [edk2-devel] " Gao, Zhichao
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 09/11] UnitTestFrameworkPkg: Add RISC-V architecture " Abner Chang
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 10/11] MdePkg/DxeServicesLib: Add RISC-V architecture Abner Chang
2020-03-27  3:21   ` Liming Gao
2020-03-06  5:36 ` [edk2/master PATCH RISC-V CI Code Changes v1 11/11] MdeModulePkg: Use LockBoxNullLib for RISC-V Abner Chang
2020-03-19  8:01   ` [edk2-devel] " Dong, Eric

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=734D49CCEBEEF84792F5B80ED585239D5C492A3A@SHSMSX104.ccr.corp.intel.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