From: "Zeng, Star" <star.zeng@intel.com>
To: "Chiu, Chasel" <chasel.chiu@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Ma, Maurice" <maurice.ma@intel.com>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH] IntelFsp2Pkg/FspSplitBin.py: Support rebasing 1.x binary.
Date: Wed, 29 May 2019 15:19:58 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB048310402FAC5D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20190529143324.15956-1-chasel.chiu@intel.com>
Shouldn't the SplitFspBinUserManual.md also be updated?
Thanks,
Star
> -----Original Message-----
> From: Chiu, Chasel
> Sent: Wednesday, May 29, 2019 10:33 PM
> To: devel@edk2.groups.io
> Cc: Ma, Maurice <maurice.ma@intel.com>; Desimone, Nathaniel L
> <nathaniel.l.desimone@intel.com>; Zeng, Star <star.zeng@intel.com>
> Subject: [PATCH] IntelFsp2Pkg/FspSplitBin.py: Support rebasing 1.x binary.
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1308
>
> Support rebasing FSP 1.X binary.
>
> Test: both FSP 2.X (Kabylake) and FSP 1.X (BroadwellDE) binary
> can be rebased successfully.
>
> Cc: Maurice Ma <maurice.ma@intel.com>
> Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
> ---
> IntelFsp2Pkg/Tools/SplitFspBin.py | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/IntelFsp2Pkg/Tools/SplitFspBin.py
> b/IntelFsp2Pkg/Tools/SplitFspBin.py
> index 2458231d09..15c8bebee2 100644
> --- a/IntelFsp2Pkg/Tools/SplitFspBin.py
> +++ b/IntelFsp2Pkg/Tools/SplitFspBin.py
> @@ -1,6 +1,6 @@
> ## @ FspTool.py
> #
> -# Copyright (c) 2015 - 2018, Intel Corporation. All rights reserved.<BR>
> +# Copyright (c) 2015 - 2019, Intel Corporation. All rights
> +reserved.<BR>
> # SPDX-License-Identifier: BSD-2-Clause-Patent # ## @@ -14,12 +14,12 @@
> import argparse
> from ctypes import *
>
> """
> -This utility supports some operations for Intel FSP 2.0 image.
> +This utility supports some operations for Intel FSP 1.x/2.x image.
> It supports:
> - - Display FSP 2.0 information header
> - - Split FSP 2.0 image into individual FSP-T/M/S/O component
> - - Rebase FSP 2.0 components to a different base address
> - - Generate FSP mapping C header file
> + - Display FSP 1.x/2.x information header
> + - Split FSP 2.x image into individual FSP-T/M/S/O component
> + - Rebase FSP 1.x/2.x components to a different base address
> + - Generate FSP 1.x/2.x mapping C header file
> """
>
> CopyRightHeaderFile = """/*
> @@ -500,8 +500,6 @@ class FirmwareDevice:
>
> fih = None
> for fsp in self.FspList:
> - if fsp.Fih.HeaderRevision < 3:
> - raise Exception("ERROR: FSP 1.x is not supported by this tool !")
> if not fih:
> fih = fsp.Fih
> else:
> @@ -713,6 +711,8 @@ def SplitFspBin (fspfile, outdir, nametemplate):
> fd.ParseFsp ()
>
> for fsp in fd.FspList:
> + if fsp.Fih.HeaderRevision < 3:
> + raise Exception("ERROR: FSP 1.x is not supported by the
> + split command !")
> ftype = fsp.Type
> if not nametemplate:
> nametemplate = fspfile
> @@ -742,6 +742,11 @@ def RebaseFspBin (FspBinary, FspComponent,
> FspBase, OutputDir, OutputFile):
>
> found = False
> for fsp in fd.FspList:
> + # Is this FSP 1.x single binary?
> + if fsp.Fih.HeaderRevision < 3:
> + found = True
> + ftype = 'X'
> + break
> ftype = fsp.Type.lower()
> if ftype == fspcomp:
> found = True
> --
> 2.13.3.windows.1
next prev parent reply other threads:[~2019-05-29 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 14:33 [PATCH] IntelFsp2Pkg/FspSplitBin.py: Support rebasing 1.x binary Chiu, Chasel
2019-05-29 15:19 ` Zeng, Star [this message]
2019-05-30 1:24 ` 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=0C09AFA07DD0434D9E2A0C6AEB048310402FAC5D@shsmsx102.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