?user
> Cc: edk2-devel@lists.01.org; Bruce Cran
> Subject: Re: [edk2] Firmware Management Protocol: CHAR16* fields in
> EFI_FIRMWARE_IMAGE_DESCRIPTOR
>
>
> > On Jul 7, 2016, at 1:27 PM, Marvin H?user
> wrote:
> >
> > Hey Bruce,
> >
> > Sorry if I
On 7/7/2016 2:06 PM, Andrew Fish wrote:
Probably worth brining it up with the UEFI Forum.
Thanks, I've just emailed them.
--
Bruce
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
On 7/7/2016 2:27 PM, Marvin H?user wrote:
I don't think these strings can ever be statically allocated. If pointers to
stack variables were used, the strings would be theoretically invalid the
moment the exposing function returns. Furthermore they can't be part oft he
struct itself as that wo
every call? So I think it is a less clear cut case.
Thanks,
Andrew Fish
> Regards,
> Marvin.
>
>> -Original Message-
>> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>> Bruce Cran
>> Sent: Thursday, July 7, 2016 9:36 PM
&g
el [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Bruce Cran
> Sent: Thursday, July 7, 2016 9:36 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Firmware Management Protocol: CHAR16* fields in
> EFI_FIRMWARE_IMAGE_DESCRIPTOR
>
> Before I go hassling the USWG,
> On Jul 7, 2016, at 12:35 PM, Bruce Cran wrote:
>
> Before I go hassling the USWG, I thought I'd check here in case anyone knows.
>
> In the Firmware Management Protocol introduced in UEFI 2.3, there's a
> EFI_FIRMWARE_IMAGE_DESCRIPTOR structure that has two CHAR16* fields,
> 'ImageIdName' a
Before I go hassling the USWG, I thought I'd check here in case anyone
knows.
In the Firmware Management Protocol introduced in UEFI 2.3, there's a
EFI_FIRMWARE_IMAGE_DESCRIPTOR structure that has two CHAR16* fields,
'ImageIdName' and 'VersionName'. The UEFI spec doesn't say anything
about me
7 matches
Mail list logo
