public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: FDF file syntax question?
Date: Thu, 12 Jan 2017 10:57:44 -0800	[thread overview]
Message-ID: <57F9E953-2F37-4487-BFAC-B2865AF784AB@apple.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6CE062@shsmsx102.ccr.corp.intel.com>


> 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



      reply	other threads:[~2017-01-12 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  9:14 FDF file syntax question? Andrew Fish
2017-01-12 14:55 ` Gao, Liming
2017-01-12 18:57   ` Andrew Fish [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=57F9E953-2F37-4487-BFAC-B2865AF784AB@apple.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