public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chiu, Chasel" <chasel.chiu@intel.com>
To: "Kuo, IanX" <ianx.kuo@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Subject: Re: [PATCH v4] MinPlatformPkg: Rebase fail when python tools path exist whitespace exist whitespace REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3412
Date: Mon, 31 May 2021 03:23:33 +0000	[thread overview]
Message-ID: <SN6PR11MB28149338D38E168DBC564292E63F9@SN6PR11MB2814.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6ba48b2f5b7676eb6bf1199e51ce691b54beff5f.1621846279.git.ianx.kuo@intel.com>


Patch has pushed: 86984c17d562fc60a6dabbc3a479d79163656a0c

> -----Original Message-----
> From: Kuo, IanX <ianx.kuo@intel.com>
> Sent: Monday, May 24, 2021 6:49 AM
> To: devel@edk2.groups.io
> Cc: Kuo, IanX <ianx.kuo@intel.com>; Chiu, Chasel <chasel.chiu@intel.com>;
> Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
> Subject: [PATCH v4] MinPlatformPkg: Rebase fail when python tools path exist
> whitespace exist whitespace REF:
> https://bugzilla.tianocore.org/show_bug.cgi?id=3412
> 
> From: IanX Kuo <ianx.kuo@intel.com>
> 
> (a) C:\Users\<UserName>\AppData\Local\Program\Python\Python38
> (b) C:\Python38
> (c) C:\Program Files\Python38
> Issue only happens on (a) and (c).
> (a) happen on <UserName> have whitespace. Ex: Tony Chen
> (c) happen on "Program Files" have whitespace.
> 
> Reviewed-by: Chasel Chiu <chasel.chiu@intel.com>
> Cc: Chasel Chiu <chasel.chiu@intel.com>
> Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
> Signed-off-by: IanX Kuo <ianx.kuo@intel.com>
> ---
>  .../Tools/Fsp/RebaseAndPatchFspBinBaseAddress.py            | 6 +++---
>  .../MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py     | 6 +++---
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git
> a/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseAndPatchFspBinBaseAddres
> s.py
> b/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseAndPatchFspBinBaseAddres
> s.py
> index 406e5ec130..f3cba2651a 100644
> ---
> a/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseAndPatchFspBinBaseAddres
> s.py
> +++ b/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseAndPatchFspBinBaseAd
> +++ dress.py
> @@ -1,6 +1,6 @@
>  ## @ RebaseAndPatchFspBinBaseAddress.py #-# Copyright (c) 2017 - 2019, Intel
> Corporation. All rights reserved.<BR>+# Copyright (c) 2017 - 2021, Intel
> Corporation. All rights reserved.<BR> # SPDX-License-Identifier: BSD-2-Clause-
> Patent # @@ -93,13 +93,13 @@ fspTBaseAddress = flashBase + fspTBaseOffset
> # Re-base FSP bin file to new address and save it as fspBinFileRebased using
> SplitFspBin.py # rebaseArguments = fspBinFilePath + " -c s m t -b " +
> str(hex(fspSBaseAddress).rstrip("L")) + " " + str(hex(fspMBaseAddress).rstrip("L"))
> + " " + str(hex(fspTBaseAddress).rstrip("L")) + " -o" + fspBinPath + " -n " +
> fspBinFileRebased-os.system(pythontool + " " + splitFspBinPath + " rebase -f" +
> rebaseArguments)+os.system('"' + pythontool + '"' + " " + splitFspBinPath + "
> rebase -f" + rebaseArguments)  # # Split FSP bin to FSP-S/M/T segments #
> splitArguments = fspBinPath + os.sep + fspBinFileRebased + " -o " + fspBinPath +
> " -n Fsp_Rebased.fd"-os.system(pythontool + " " + splitFspBinPath + " split -f" +
> splitArguments)+os.system('"' + pythontool + '"' + " " + splitFspBinPath + " split -
> f" + splitArguments)  # # Patch dsc file with the re-based FSP-S/M/T address, so
> internally build will use the same.diff --git
> a/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py
> b/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py
> index fb4cf4f9b7..b7e4bcf5f9 100644
> --- a/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py
> +++ b/Platform/Intel/MinPlatformPkg/Tools/Fsp/RebaseFspBinBaseAddress.py
> @@ -1,6 +1,6 @@
>  ## @ RebaseFspBinBaseAddress.py #-# Copyright (c) 2019, Intel Corporation. All
> rights reserved.<BR>+# Copyright (c) 2019 - 2021, Intel Corporation. All rights
> reserved.<BR> # SPDX-License-Identifier: BSD-2-Clause-Patent # @@ -87,12
> +87,12 @@ fspTBaseAddress = flashBase + fspTBaseOffset  # Re-base FSP bin
> file to new address and save it as fspBinFileRebased using SplitFspBin.py #
> rebaseArguments = fspBinFilePath + " -c s m t -b " +
> str(hex(fspSBaseAddress).rstrip("L")) + " " + str(hex(fspMBaseAddress).rstrip("L"))
> + " " + str(hex(fspTBaseAddress).rstrip("L")) + " -o" + fspBinPath + " -n " +
> fspBinFileRebased-os.system(pythontool + " " + splitFspBinPath + " rebase -f" +
> rebaseArguments)+os.system('"' + pythontool + '"' + " " + splitFspBinPath + "
> rebase -f" + rebaseArguments)  # # Split FSP bin to FSP-S/M/T segments #
> splitArguments = fspBinPath + os.sep + fspBinFileRebased + " -o " + fspBinPath +
> " -n Fsp_Rebased.fd"-os.system(pythontool + " " + splitFspBinPath + " split -f" +
> splitArguments)+os.system('"' + pythontool + '"' + " " + splitFspBinPath + " split -
> f" + splitArguments)  exit(0)--
> 2.27.0.windows.1


      parent reply	other threads:[~2021-05-31  3:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 22:38 [PATCH v3] MinPlatformPkg/Fsp: Rebase fail when python tools path exist whitespace REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3412 IanX Kuo
2021-05-24 10:09 ` Chiu, Chasel
2021-05-31  3:23 ` Chiu, Chasel [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=SN6PR11MB28149338D38E168DBC564292E63F9@SN6PR11MB2814.namprd11.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