public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
	"Song, BinX" <binx.song@intel.com>,
	 "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] IntelFsp2Pkg: Delete useless external TempRamInitApi API
Date: Thu, 3 Aug 2017 15:04:37 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D75F4AB@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503A98296A@shsmsx102.ccr.corp.intel.com>

Jiewen:
  The change is in SecFspSecPlatformLibNull. This library instance provides the dummy function. It should not be used by any real FSP. We meet with the build issue with /WHOLEARCHIVE option. Because this library depends on the external TempRamInitApi(), but FspSecCoreS and FspSecCoreT don't provide TempRamInitApi(). Then, FspSecCoreS and FspSecCoreT will build failure. To fix this build failure, we choose to remove this unnecessary dependency. 

> >  global ASM_PFX(ProtectedModeEntryPoint)
> >  ASM_PFX(ProtectedModeEntryPoint):
> > -  ;
> > -  ; Dummy function. Consume 2 API to make sure they can be linked.
> > -  ;	

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Yao, Jiewen
> Sent: Thursday, August 3, 2017 9:03 PM
> To: Song, BinX <binx.song@intel.com>; edk2-devel@lists.01.org
> Cc: Giri P Mudusuru <giri.p.mudusuru@intel.com>
> Subject: Re: [edk2] [PATCH] IntelFsp2Pkg: Delete useless external TempRamInitApi API
> 
> Hi
> May I know what test you have done to remove this?
> 
> Have you built a real FSP and boot it with FSP Wrapper?
> 
> Thank you
> Yao Jiewen
> 
> > -----Original Message-----
> > From: Song, BinX
> > Sent: Thursday, August 3, 2017 1:47 PM
> > To: edk2-devel@lists.01.org
> > Cc: Yao, Jiewen <jiewen.yao@intel.com>; Giri P Mudusuru
> > <giri.p.mudusuru@intel.com>
> > Subject: [PATCH] IntelFsp2Pkg: Delete useless external TempRamInitApi API
> >
> > - Delete useless external TempRamInitApi API to fix /WHOLEARCHIVE build
> >   error with VS2015 tool chain
> >
> > Cc: Jiewen Yao <jiewen.yao@intel.com>
> > Cc: Giri P Mudusuru <giri.p.mudusuru@intel.com>
> > Contributed-under: TianoCore Contribution Agreement 1.0
> > Signed-off-by: Bell Song <binx.song@intel.com>
> > ---
> >  IntelFsp2Pkg/Library/SecFspSecPlatformLibNull/Ia32/Flat32.nasm | 7 -------
> >  1 file changed, 7 deletions(-)
> >
> > diff --git a/IntelFsp2Pkg/Library/SecFspSecPlatformLibNull/Ia32/Flat32.nasm
> > b/IntelFsp2Pkg/Library/SecFspSecPlatformLibNull/Ia32/Flat32.nasm
> > index 122eb9e..ee78312 100644
> > --- a/IntelFsp2Pkg/Library/SecFspSecPlatformLibNull/Ia32/Flat32.nasm
> > +++ b/IntelFsp2Pkg/Library/SecFspSecPlatformLibNull/Ia32/Flat32.nasm
> > @@ -16,8 +16,6 @@
> >  ; Define assembler characteristics
> >  ;
> >
> > -extern   ASM_PFX(TempRamInitApi)
> > -
> >  SECTION .text
> >
> >  %macro RET_ESI  0
> > @@ -66,11 +64,6 @@ ASM_PFX(SecPlatformInit):
> >  ;----------------------------------------------------------------------------
> >  global ASM_PFX(ProtectedModeEntryPoint)
> >  ASM_PFX(ProtectedModeEntryPoint):
> > -  ;
> > -  ; Dummy function. Consume 2 API to make sure they can be linked.
> > -  ;	
> > -  mov  eax, ASM_PFX(TempRamInitApi)
> > -
> >    ; Should never return
> >    jmp  $
> >
> > --
> > 2.10.2.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-08-03 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  5:47 [PATCH] IntelFsp2Pkg: Delete useless external TempRamInitApi API Song, BinX
2017-08-03 13:03 ` Yao, Jiewen
2017-08-03 15:04   ` Gao, Liming [this message]
2017-08-17  7:53     ` Yao, Jiewen
2017-08-17  8:00       ` Gao, Liming

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=4A89E2EF3DFEDB4C8BFDE51014F606A14D75F4AB@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