public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Leif Lindholm <leif@nuviainc.com>,
	"Chen, Gilbert" <gilbert.chen@hpe.com>,
	"Schaefer, Daniel (DualStudy)" <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: Fri, 20 Mar 2020 01:16:31 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9EEC608@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <15edadf1af734facb5b914b7986365ac@intel.com>

Liming,

I agree that spec updates would be good so the CPU arch
name RISCV64 can be reserved.

However, I believe the current specs define their EBNF
to be flexible and support new CPU archs without a spec
change.  As long as BaseTools follows the EBNF, no build
tool changes should be required to support a new arch.

For example the EBNF below supports <OA> that can be
and name.

<OA> ::= (a-zA-Z)(a-zA-Z0-9)*
<arch> ::= {"IA32"} {"X64"} {"EBC"} {<OA>} {"COMMON"}

I do not think any of the RISCV64 code changes should be
blocked by spec updates or BaseTools changes.

Do you agree?

Thanks,

Mike


> -----Original Message-----
> From: Gao, Liming <liming.gao@intel.com>
> Sent: Wednesday, March 11, 2020 11:47 PM
> To: Chang, Abner (HPS SW/FW Technologist)
> <abner.chang@hpe.com>; devel@edk2.groups.io; Ni, Ray
> <ray.ni@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>; Chen, Gilbert
> <gilbert.chen@hpe.com>; Schaefer, Daniel (DualStudy)
> <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.
> 
> Edk2 spec are listed in
> https://github.com/tianocore/tianocore.github.io/wiki/E
> DK-II-Specifications
> 
> This change requires to update INF/DEC/DSC/FDF/Build
> spec. You can find their github repo in the above link.
> Then, create git patch for the change.
> 
> Thanks
> Liming
> -----Original Message-----
> From: Chang, Abner (HPS SW/FW Technologist)
> <abner.chang@hpe.com>
> Sent: 2020年3月12日 14:27
> To: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>;
> Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>; Chen, Gilbert
> <gilbert.chen@hpe.com>; Schaefer, Daniel (DualStudy)
> <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.
> 
> 
> 
> > -----Original Message-----
> > From: devel@edk2.groups.io
> [mailto:devel@edk2.groups.io] On Behalf Of
> > Ni, Ray
> > Sent: Thursday, March 12, 2020 1:40 PM
> > To: devel@edk2.groups.io; Chang, Abner (HPS SW/FW
> Technologist)
> > <abner.chang@hpe.com>; Gao, Liming
> <liming.gao@intel.com>; Kinney,
> > Michael D <michael.d.kinney@intel.com>
> > Cc: Leif Lindholm <leif@nuviainc.com>; Chen, Gilbert
> > <gilbert.chen@hpe.com>; Schaefer, Daniel (DualStudy)
> > <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.
> >
> > Abner,
> > Has the change to BaseTools supporting new ARCH been
> merged?
> No, not yet. The whole changes to RISCV64 ARCH is in
> the separate huge set of patches. We have three sets of
> RISC-V edk2 port.
> 
> 1.  Patches for RISC-V EDK2  CI enablement 2.  Patches
> for edk2 modules other than RISC-V ones, which fix the
> issues for building  packages respectively on RISC-V
> arch.
> 3 . RISC-V edk2 port
> 
> The patch needs your Reviewed-by is belong to #2. We
> can have a PR for #3 and trigger CI testing once #1 and
> #2 are merged to master.
> 
> >
> > Liming, Mike,
> > Does INF specification need to be updated for this
> new ARCH?
> Good question, how to submit the changes to these
> specs?
> 
> >
> > 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__bugzilla.tianoc
> > > or
> > > e.org_show-5Fbug.cgi-3Fid-
> > 3D2562&d=DwIFAg&c=C5b8zRQO1miGmBeVZ2LFWg&r=_
> > >
> >
> SN6FZBN4Vgi4Ulkskz6qU3NYRO03nHp9P7Z5q59A3E&m=hdx0Amnugj
> VyUKB
> > Egf8jkKDBs
> > > rX81gAFwMi_pmEH2-
> > g&s=7pymX9FxJA5arZHTI9zd_qr3b2Jk2tx3OVff9UkxoW4&e=
> > >
> > > 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://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__edk2.groups.io_g_
> > >
> >
> devel_message_55584&d=DwIFAg&c=C5b8zRQO1miGmBeVZ2LFWg&r
> =_SN
> > 6FZBN4Vgi4U
> > >
> >
> lkskz6qU3NYRO03nHp9P7Z5q59A3E&m=hdx0AmnugjVyUKBEgf8jkKD
> BsrX81g
> > AFwMi_pm
> > > EH2-g&s=WRly7Kh6eK9ppe59UcH-
> U5xBt7Lsp2K38n1jfPO1mKg&e=
> > > Mute This Topic:
> > > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__groups.io_mt_7176
> > >
> >
> 7323_1712937&d=DwIFAg&c=C5b8zRQO1miGmBeVZ2LFWg&r=_SN6FZ
> BN4V
> > gi4Ulkskz6q
> > >
> >
> U3NYRO03nHp9P7Z5q59A3E&m=hdx0AmnugjVyUKBEgf8jkKDBsrX81g
> AFwMi
> > _pmEH2-g&s
> > > =wuAcZWk-ZDd7lyPIz4_Ph3LwBqgNanz3lag5-evIjns&e=
> > > Group Owner: devel+owner@edk2.groups.io
> > > Unsubscribe:
> https://urldefense.proofpoint.com/v2/url?u=https-
> >
> 3A__edk2.groups.io_g_devel_unsub&d=DwIFAg&c=C5b8zRQO1mi
> GmBeVZ2
> >
> LFWg&r=_SN6FZBN4Vgi4Ulkskz6qU3NYRO03nHp9P7Z5q59A3E&m=hd
> x0Amn
> > ugjVyUKBEgf8jkKDBsrX81gAFwMi_pmEH2-
> g&s=dAyFUfd07U1tFQRk-
> > aK_WytEXVsMhZszgAPW8IoXljA&e=   [ray.ni@intel.com]
> > > -=-=-=-=-=-=
> >
> >
> > 
> 


  reply	other threads:[~2020-03-20  1:16 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   ` [edk2-devel] " Ni, Ray
2020-03-12  6:27     ` Abner Chang
2020-03-12  6:47       ` Liming Gao
2020-03-20  1:16         ` Michael D Kinney [this message]
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=E92EE9817A31E24EB0585FDF735412F5B9EEC608@ORSMSX113.amr.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