From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, chasel.chiu@intel.com
Cc: Michael Kubacki <michael.a.kubacki@intel.com>,
Ankit Sinha <ankit.sinha@intel.com>,
Nate DeSimone <nathaniel.l.desimone@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/4] Auto configure Fsp*BaseAddress PCD
Date: Mon, 29 Jul 2019 15:47:04 +0200 [thread overview]
Message-ID: <9737c4be-9667-ddd5-5267-a0c27412a3be@redhat.com> (raw)
In-Reply-To: <20190729110715.2312-1-chasel.chiu@intel.com>
On 07/29/19 13:07, Chiu, Chasel wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1863
>
> PcdFsp*BaseAddress now will be updated in FDF basing
> on flash map.
> DSC will only define types of those PCDs and always
> having 0 as default.
> New script added to only rebase FSP binary without
> patching DSC file.
>
> Test: interanl platform booted with this patch.
>
> Cc: Michael Kubacki <michael.a.kubacki@intel.com>
> Cc: Ankit Sinha <ankit.sinha@intel.com>
> Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
>
> Chasel Chiu (4):
> MinPlatformPkg: Auto configure Fsp*BaseAddress PCD
> Platform/Intel: Auto configure Fsp*BaseAddress PCD
> KabylakeOpenBoardPkg: Auto configure Fsp*BaseAddress PCD
> ClevoOpenBoardPkg: Auto configure Fsp*BaseAddress PCD
>
> Platform/Intel/ClevoOpenBoardPkg/N1xxWU/OpenBoardPkg.fdf | 3 +++
> Platform/Intel/ClevoOpenBoardPkg/N1xxWU/OpenBoardPkgPcd.dsc | 12 +++++++++---
> Platform/Intel/KabylakeOpenBoardPkg/KabylakeRvp3/OpenBoardPkg.fdf | 3 +++
> Platform/Intel/KabylakeOpenBoardPkg/KabylakeRvp3/OpenBoardPkgPcd.dsc | 12 +++++++++---
> Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Platform/Intel/build_bios.py | 7 ++-----
> 6 files changed, 122 insertions(+), 11 deletions(-)
> create mode 100644 Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py
>
I think the classification on TianoCore BZ#1863 is wrong. It should be
"EDK2 Platforms", probably. Please update the BZ.
Accordingly, the subject prefix on this patch series should not be
"PATCH", but "edk2-platforms PATCH". No need to resend the v1 patch
series just for this, but if you send a v2, please set the correct
subject prefix:
git format-patch -v2 --subject-prefix='edk2-platforms PATCH' ...
Thanks
Laszlo
next prev parent reply other threads:[~2019-07-29 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 11:07 [PATCH 0/4] Auto configure Fsp*BaseAddress PCD Chiu, Chasel
2019-07-29 11:07 ` [PATCH 1/4] MinPlatformPkg: " Chiu, Chasel
2019-07-30 22:18 ` Nate DeSimone
2019-07-31 18:58 ` [edk2-devel] " Sinha, Ankit
2019-07-29 11:07 ` [PATCH 2/4] Platform/Intel: " Chiu, Chasel
2019-07-30 22:18 ` [edk2-devel] " Nate DeSimone
2019-07-31 18:59 ` Sinha, Ankit
2019-07-29 11:07 ` [PATCH 3/4] KabylakeOpenBoardPkg: " Chiu, Chasel
2019-07-30 22:19 ` [edk2-devel] " Nate DeSimone
2019-07-31 18:59 ` Sinha, Ankit
2019-07-29 11:07 ` [PATCH 4/4] ClevoOpenBoardPkg: " Chiu, Chasel
2019-07-30 22:19 ` [edk2-devel] " Nate DeSimone
2019-07-31 19:00 ` Sinha, Ankit
2019-07-29 13:47 ` Laszlo Ersek [this message]
2019-07-30 1:07 ` [edk2-devel] [PATCH 0/4] " Chiu, Chasel
2019-07-30 3:46 ` Liming Gao
2019-07-30 3:49 ` Chiu, Chasel
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=9737c4be-9667-ddd5-5267-a0c27412a3be@redhat.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