On Wed, Sep 12, 2012 at 9:57 AM, Pant, Alok <[email protected]> wrote:
> A) I removed the GUID defined per your suggestion and it still fails. I did
> this similar failed experiment in NT32Pkg as a build test. Attach is the
> patch if you or others have suggestions..It looks to me EFI_COMPRESSION has
> some issues.
>
I opened Nt32Pkg.fdf, and now I see where your original code came
from. I'm not familiar with using 'GUIDED {' on it's own like that,
but if it is in Nt32Pkg.fdf, then it most likely is valid.
> FILE SMM = $(NAMED_GUID) {
> SMM_DEPEX SMM_DEPEX Optional $(INF_OUTPUT)/$(MODULE_NAME).depex
> COMPRESS PI_STD {
> #<Per Justin> GUIDED {
> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
> }
> #<Per Justin> }
> }
I tried making a similar change to OVMF, and the syntax seems to work
there. I was using the latest trunk, rather than "UDK.SPI.UP1", but I
would be surprised if this was the issue.
> b) The below fixes the build issue but the SMM drivers are no longer loaded.
> I need to spend some time to understand if I need to do changes in BIOS
> runtime code etc.
> FILE SMM = $(NAMED_GUID) {
> SMM_DEPEX SMM_DEPEX Optional $(INF_OUTPUT)/$(MODULE_NAME).depex
> GUIDED A31280AD-481E-41B6-95E8-127F4C984779 PROCESSING_REQUIRED = TRUE {
> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
> }
> }
This would require usage of the TianoDecompress Library in the
platform. It sounds like this is not what you need, but it is
interesting that it builds, while the other fails.
I can't think of anything else for you to try right now.
-Jordan
> -----Original Message-----
> From: Jordan Justen [mailto:[email protected]]
> Sent: Wednesday, September 12, 2012 1:22 AM
> To: Pant, Alok
> Cc: [email protected]
> Subject: Re: [edk2-buildtools] EDKII build issue: Can SMM driver be
> compressed using current toolset
>
> On Tue, Sep 11, 2012 at 3:56 PM, Pant, Alok <[email protected]> wrote:
>> I am using UDK.SPI.UP1 source code to build some SMM drivers. Everything is
>> fine as long as drivers are uncompressed; but when I change the fdf file as
>> below to attempt to compress the SMM driver binary, I get the following
>> error. Any suggestion on what I may be doing wrong. Does the tool support
>> SMM driver compression?
>>
>> Thanks
>>
>> -Alok Pant
>>
>> Change in FDF file
>>
>> [Rule.Common.DXE_SMM_DRIVER]
>> FILE SMM = $(NAMED_GUID) {
>> SMM_DEPEX SMM_DEPEX Optional $(INF_OUTPUT)/$(MODULE_NAME).depex
>> COMPRESS PI_STD {
>> GUIDED {
>> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
>> }
>> }
>
> That doesn't appear to be the correct syntax for compression. How about these?
>
> EFI compression:
> COMPRESS PI_STD {
> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
> }
>
> TianoCompress compression:
> GUIDED A31280AD-481E-41B6-95E8-127F4C984779 PROCESSING_REQUIRED = TRUE {
> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
> }
>
> LZMA compression:
> GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {
> PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
> }
>
> -Jordan
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-buildtools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel
