From: "Abner Chang" <abner.chang@hpe.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH v1 0/1] BaseTools: BaseTools changes for RISC-V platform.
Date: Tue, 21 Apr 2020 02:41:03 +0000 [thread overview]
Message-ID: <TU4PR8401MB0429538AEDD42B75C3DE045DFFD50@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <BN6PR11MB39724A939A2275B78735989080D50@BN6PR11MB3972.namprd11.prod.outlook.com>
PATCH V3 sent.
> -----Original Message-----
> From: Gao, Liming [mailto:liming.gao@intel.com]
> Sent: Tuesday, April 21, 2020 8:57 AM
> To: devel@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
> <abner.chang@hpe.com>
> Subject: RE: [edk2-devel] [PATCH v1 0/1] BaseTools: BaseTools changes for
> RISC-V platform.
>
> For this change, I suggest to separate it to three patches. One is for
> tools_def.template, another is for Build Python, last one is for BaseTools C
> tool.
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Chang,
> Abner (HPS SW/FW Technologist)
> Sent: 2020年4月10日 15:47
> To: devel@edk2.groups.io
> Cc: Chang, Abner (HPS SW/FW Technologist) <abner.chang@hpe.com>
> Subject: [edk2-devel] [PATCH v1 0/1] BaseTools: BaseTools changes for RISC-
> V platform.
>
> BZ for entire RISC-V edk2 port,
> INVALID URI REMOVED
> 3A__bugzilla.tianocore.org_show-5Fbug.cgi-3Fid-
> 3D2672&d=DwIFAg&c=C5b8zRQO1miGmBeVZ2LFWg&r=_SN6FZBN4Vgi4Ulks
> kz6qU3NYRO03nHp9P7Z5q59A3E&m=-
> F9g6mAm7GCIMh1Z99KMnTQ87UruBvEOFadrCxs6Fbs&s=sfGS0fehOwf4GO0
> C1RIwVQJU9RDUWNCfX6t9wxrc8QA&e=
>
> These commits are verified by below PR,
> https://github.com/tianocore/edk2/pull/512
>
> Abner Chang (1):
> BaseTools: BaseTools changes for RISC-V platform.
>
> BaseTools/Source/C/Common/PeCoffLib.h | 9 +
> BaseTools/Source/C/GenFw/elf_common.h | 62 ++++
> .../C/Include/IndustryStandard/PeImage.h | 6 +
> BaseTools/Source/C/Common/BasePeCoff.c | 15 +-
> BaseTools/Source/C/Common/PeCoffLoaderEx.c | 86 ++++++
> BaseTools/Source/C/GenFv/GenFvInternalLib.c | 128 +++++++-
> BaseTools/Source/C/GenFw/Elf32Convert.c | 5 +-
> BaseTools/Source/C/GenFw/Elf64Convert.c | 282 +++++++++++++++++-
> BaseTools/Conf/tools_def.template | 53 +++-
> BaseTools/Source/Python/Common/DataType.py | 5 +-
> BaseTools/Source/Python/build/buildoptions.py | 6 +-
> 11 files changed, 638 insertions(+), 19 deletions(-)
>
> --
> 2.25.0
>
>
>
prev parent reply other threads:[~2020-04-21 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <160467C9AEFA0F66.7555@groups.io>
2020-04-21 0:57 ` [edk2-devel] [PATCH v1 0/1] BaseTools: BaseTools changes for RISC-V platform Liming Gao
2020-04-21 2:41 ` Abner Chang [this message]
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=TU4PR8401MB0429538AEDD42B75C3DE045DFFD50@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.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