> On Jul 18, 2016, at 9:07 AM, Michael Zimmermann <sigmaepsilo...@gmail.com> > wrote: > > > I don't need/use XIP or relocation(would the latter make a difference > anyway?). > > Also the difference between FD and FV seems to be terminology only, because > YOURPLATFORM.fd has the same checksum as FVMAIN_COMPACT.Fv. > > What I successfully tested as a workaround is reading > EFI_FV_TAKEN_SIZE from FVMAIN_COMPACT.Fv.map and strip the file to that > size. > That seems to work, but I'm not sure if it's exact, because there are still > a few 0xff bytes left and I'm not sure if these really are for aligning the > size only. >
Michael, The FD is a collection of FVs and Data regions output by the build system. If all you have is an FV you should just use that. You can reduce the padding by setting the BlockSize smaller. The FvAlignment value (commonly 16) would be a good value to try. Any padding after that is coming from the FD creation: https://github.com/tianocore/edk2/blob/master/OvmfPkg/OvmfPkgX64.fdf#L91 0x100000|0xA00000 gUefiOvmfPkgTokenSpaceGuid.PcdOvmfDxeMemFvBase|gUefiOvmfPkgTokenSpaceGuid.PcdOvmfDxeMemFvSize FV = DXEFV For example This statement in the [FD.MEMFD] section will cause this region of the FLASH to get padded out if the FV is smaller than 0xA00000 The FV will start with an EFI_FIRMWARE_VOLUME_HEADER, https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Pi/PiFirmwareVolume.h#L105 , so you can programmatically figure out how big it is if you need to copy it. Thanks, Andrew Fish > Thanks > Michael > > On Mon, Jul 18, 2016 at 5:28 PM, Andrew Fish <af...@apple.com> wrote: > >> >>> On Jul 17, 2016, at 11:02 PM, Michael Zimmermann < >> sigmaepsilo...@gmail.com> wrote: >>> >>> >>> Hi, >>> >>> I noticed that the size of YOURPLATFORM.fd always equals the size >> specified >>> in your fdf >>> i.e. 4MB for 'Size = 0x00400000|gArmTokenSpaceGuid.PcdFdSize'. >>> >>> I don't know much about the case where this gets flashed to a nand and >>> executed in place, but when using edk2 on a ARM PrePi device with edk2 >>> loaded into RAM, this looks like a huge waste of storage memory and >> loading >>> time to me. >>> >>> So, is it really important to have multiple MB(depending of you fv size >>> ofc) of 0xff appended to the firmware or is there a fdf option or >>> post-compilation tool to remove this? >>> >> >> The YOURPLATFORM.fd is a Flash Device (.fd) and thus there is an >> assumption it is a fixed size. If you want a flexible size you can use an >> FV. Are you dependent on relocating the code so it can XIP? Is that what if >> forcing the use of an FD? >> >> Just trying to figure out if what you are really asking for is the ability >> to relocate an FV that is only as big as required? Maybe that is an FD, >> maybe not? >> >> Short term if your FD is just a single FV you can use a PCD to know the >> size and only copy that much data to the RAM. You would have to manually >> pick an FD size that did not waist too much storage. >> >> Thanks, >> >> Andrew Fish >> >>> Thanks >>> Michael >>> _______________________________________________ >>> edk2-devel mailing list >>> edk2-devel@lists.01.org >>> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_edk2-2Ddevel&d=CwICAg&c=Hw-EJUFt2_D9PK5csBJ29kRV40HqSDXWTLPyZ6W8u84&r=4sdzHKz0eU1vXqaUySVmyA&m=Kr0PunsxtwGLmV7IsSEodsro5Wwu2oRxRh1L7fFpt3w&s=FXzJ7wYg-xu4aJ-6YGBqB4GTUNMVu1W9h8mqqf864YQ&e= >> >> > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_edk2-2Ddevel&d=CwICAg&c=Hw-EJUFt2_D9PK5csBJ29kRV40HqSDXWTLPyZ6W8u84&r=4sdzHKz0eU1vXqaUySVmyA&m=GBYUQYXoyDqknWeJcI64xlIkHnhnVmabgBV1ABmDeZs&s=QSUxiPKjBWf7bkI3IIL0E8JliL4vuwEWURFyB2oQQ0E&e= _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
