public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Wiki] Draft of documentation for Signed Capsule Feature
Date: Thu, 10 Nov 2016 01:59:41 +0000	[thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C50386CDB8F@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F56484280E@ORSMSX113.amr.corp.intel.com>

Ah, Mike. You are right.

I will remove them. Good catch.

From: Kinney, Michael D
Sent: Thursday, November 10, 2016 2:42 AM
To: Yao, Jiewen <jiewen.yao@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: RE: [Wiki] Draft of documentation for Signed Capsule Feature

Jiewen,

Thanks for the feedback.  I think you are saying that the support for the
EFI_OS_INDICATIONS_FILE_CAPSULE_DELIVERY_SUPPORTED is not implemented.
Right?

In MdeModulePkg/Application/CapsuleApp, I see the following 2 unused #defines:

  #define EFI_CAPSULE_FROM_FILE_DIR                           L"\\EFI\\UpdateCapsule\\<file:///\\EFI\UpdateCapsule\>"
  #define EFI_OS_INDICATIONS_FILE_CAPSULE_DELIVERY_SUPPORTED  0x0000000000000004

Should these be removed?

I have updated the Wiki.

Mike

> -----Original Message-----
> From: Yao, Jiewen
> Sent: Tuesday, November 8, 2016 8:57 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>; edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
> Cc: Yao, Jiewen <jiewen.yao@intel.com<mailto:jiewen.yao@intel.com>>
> Subject: RE: [Wiki] Draft of documentation for Signed Capsule Feature
>
> HI Mike
> Thanks for drafting this WIKI page.
>
> I have some minor suggestion on https://github.com/mdkinney/edk2/wiki/Capsule-
> Based-Firmware-Update-and-Firmware-Recovery
>
> 1) *[UEFI] OsIndicationsSupported and OsIndications UEFI Variables
> ==> Current EDKII signed capsule solution does not support capsule on disk
> feature or OsIndications. Can we remove this line or say "it is not supported in
> current version" to avoid confusing?
>
> 2) *[PI] Recovery Block I/O PPI
> ==> I think Recovery Block I/O 2 PPI should also be included.
>
> Thank you
> Yao Jiewen
>
> > -----Original Message-----
> > From: Kinney, Michael D
> > Sent: Wednesday, November 9, 2016 1:54 AM
> > To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>; Kinney, Michael D
> > <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>; Yao, Jiewen <jiewen.yao@intel.com<mailto:jiewen.yao@intel.com>>
> > Subject: [Wiki] Draft of documentation for Signed Capsule Feature
> >
> > Hello,
> >
> > I have started a draft of Wiki pages that describe how to use
> > and verify the Signed Capsule feature from Jiewen Yao.
> >
> > I have focused this first draft on the system firmware update
> > use case for signed capsules.
> >
> > https://github.com/mdkinney/edk2/wiki/Capsule-Based-Firmware-Update-a
> > nd-Firmware-Recovery
> >
> > https://github.com/mdkinney/edk2/wiki/Capsule-Based-System-Firmware-U
> > pdate
> >
> > Please review this content and provide feedback.
> >
> > I will work on the remaining 3 signed capsule use cases while
> > the content for this fist use case is reviewed.
> >
> > I plan to add this content to the edk2 Wiki once the reviews are
> > completed.
> >
> > Thanks,
> >
> > Mike
> >


      reply	other threads:[~2016-11-10  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 17:54 [Wiki] Draft of documentation for Signed Capsule Feature Kinney, Michael D
2016-11-09  4:57 ` Yao, Jiewen
2016-11-09 18:41   ` Kinney, Michael D
2016-11-10  1:59     ` Yao, Jiewen [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=74D8A39837DF1E4DA445A8C0B3885C50386CDB8F@shsmsx102.ccr.corp.intel.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