On Tue, Jan 25, 2022 at 08:50:54AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > { 'struct' : 'FirmwareMappingFlash',
> > > - 'data' : { 'executable' : 'FirmwareFlashFile',
> > > - 'nvram-template' : 'FirmwareFlashFile' } }
> > > + 'data' : { 'mode': 'FirmwareFlashMode',
>
Hi,
> > { 'struct' : 'FirmwareMappingFlash',
> > - 'data' : { 'executable' : 'FirmwareFlashFile',
> > - 'nvram-template' : 'FirmwareFlashFile' } }
> > + 'data' : { 'mode': 'FirmwareFlashMode',
> > + 'executable' : 'FirmwareFlashFile',
> > +
+Gerd & David.
On 21/1/22 16:34, Daniel P. Berrangé wrote:
The current firmware descriptor schema for flash requires that both the
executable to NVRAM template paths be provided. This is fine for the
most common usage of EDK2 builds in virtualization where the separate
_CODE and _VARS files are
The current firmware descriptor schema for flash requires that both the
executable to NVRAM template paths be provided. This is fine for the
most common usage of EDK2 builds in virtualization where the separate
_CODE and _VARS files are provided.
With confidential computing technology like AMD SEV
