From: TVKR <tresko1@gmail.com>
To: Igor Skochinsky <skochinsky@gmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: UEFI Image Attribute
Date: Mon, 6 Nov 2017 08:58:37 -0600 [thread overview]
Message-ID: <CAD+hite+eWV+hukMTijJHE_yyyNgB2H=uSViaiJtP9yEJQH0RA@mail.gmail.com> (raw)
In-Reply-To: <AM5PR10MB0339967CC8881E5F19FFC2EFF85D0@AM5PR10MB0339.EURPRD10.PROD.OUTLOOK.COM>
Thanks for the reply Igor.
Yes, I was referring to the AttributesSetting of the
EFI_FIRMWARE_IMAGE_DESCRIPTOR which is read as part of the GetImageInfo
service of the FMP on a device.
So,if the device sets this attributes, does it mean that its UEFI driver's
FMP implementation can ONLY support firmware files created as per the PI
spec's FV/FFS format?
Regards
On Fri, Nov 3, 2017 at 2:38 PM, Igor Skochinsky <skochinsky@gmail.com>
wrote:
> Hi,
>
> Do you mean the one in EFI_FIRMWARE_IMAGE_DESCRIPTOR?
>
> My guess is it means “UEFI firmware image”, i.e. a set of firmware volumes
> ready for flashing (an .fd file in some contexts), as opposed to a non-UEFI
> firmware such as EC, BMC or some other variation.
>
> --
> WBR, Igor.
> _____________________________
> From: TVKR <tresko1@gmail.com>
> Sent: Friday, November 3, 2017 18:02
> Subject: [edk2] UEFI Image Attribute
> To: <edk2-devel@lists.01.org>
>
>
> What does the IMAGE_ATTRIBUTE_UEFI_IMAGE attribute mean? The spec says that
> "image is an EFI compatible image", but what that mean exactly?
>
> Thanks
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
>
>
prev parent reply other threads:[~2017-11-06 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 17:01 UEFI Image Attribute TVKR
2017-11-03 19:38 ` Igor Skochinsky
2017-11-06 14:58 ` TVKR [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='CAD+hite+eWV+hukMTijJHE_yyyNgB2H=uSViaiJtP9yEJQH0RA@mail.gmail.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