FDF file syntax question?

FDF file syntax question?

[Andrew Fish]

Is there a way to make the FV defined in the FD section be only big enough to contain the data? The remaining area could be 0xFF (erase value). If the FV is read only there is no point reading the extra data from the FLASH device if all the bytes are 0xFF. 

For example if we make an FV to be compressed the [options] section in the Build output only has the block size, but if it comes from the FD section then you get a base address and block count. 

Thanks,

Andrew Fish

Re: FDF file syntax question?

[Gao, Liming]

Andrew:
  So, this requests not to set FV size same to FD region size when this FV is placed into FD region. I think one way to do it. In [FD] section, FILE statement is used to point to the generated XXX.Fv image. And, [FV] section includes this FV block size and base address, but no block number. But, I suggest you submit one feature request in Bugzilla for BaseTools. We can enhance BaseTools to support this usage model. 

Thanks
Liming
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Andrew Fish
Sent: Wednesday, January 11, 2017 5:15 PM
To: edk2-devel <edk2-devel@lists.01.org>
Subject: [edk2] FDF file syntax question?

Is there a way to make the FV defined in the FD section be only big enough to contain the data? The remaining area could be 0xFF (erase value). If the FV is read only there is no point reading the extra data from the FLASH device if all the bytes are 0xFF. 

For example if we make an FV to be compressed the [options] section in the Build output only has the block size, but if it comes from the FD section then you get a base address and block count. 

Thanks,

Andrew Fish


_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: FDF file syntax question?

[Andrew Fish]

> On Jan 12, 2017, at 6:55 AM, Gao, Liming <liming.gao@intel.com> wrote:
> 
> Andrew:
>  So, this requests not to set FV size same to FD region size when this FV is placed into FD region. I think one way to do it. In [FD] section, FILE statement is used to point to the generated XXX.Fv image. And, [FV] section includes this FV block size and base address, but no block number. But, I suggest you submit one feature request in Bugzilla for BaseTools. We can enhance BaseTools to support this usage model. 
> 

Liming,

Thanks for the ideas about FDF syntax. 

I actually had another idea. I was thinking of storing "actual size" of the FV (excluding all the pad bytes at the end of the FV)  in the FV extended header. That way no information is lost. I'll let you know what I come up with. 

Thanks,

Andrew Fish

> Thanks
> Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Andrew Fish
> Sent: Wednesday, January 11, 2017 5:15 PM
> To: edk2-devel <edk2-devel@lists.01.org>
> Subject: [edk2] FDF file syntax question?
> 
> Is there a way to make the FV defined in the FD section be only big enough to contain the data? The remaining area could be 0xFF (erase value). If the FV is read only there is no point reading the extra data from the FLASH device if all the bytes are 0xFF. 
> 
> For example if we make an FV to be compressed the [options] section in the Build output only has the block size, but if it comes from the FD section then you get a base address and block count. 
> 
> Thanks,
> 
> Andrew Fish
> 
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel