public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [RFC v3 0/4] Add FmpDevicePkg
Date: Thu, 31 May 2018 13:13:40 +0200	[thread overview]
Message-ID: <CAKv+Gu_PNYKBU-5JOzbVPLKnuoQFV=MXB_=ziCOrqqjmk=A0tg@mail.gmail.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8A62B76@ORSMSX113.amr.corp.intel.com>

On 30 May 2018 at 17:15, Kinney, Michael D <michael.d.kinney@intel.com> wrote:
> Hi Add,
>
> The FmpDevicePkg is a different way to produce
> FMP and the recommendation will be to use this
> one instead of the existing one.  The concept
> is to provide a simpler way to produce an FMP
> with a library instance and a few PCD settings.
> It has greater flexibility in managing public
> keys, supports multiple public keys per FMP,
> and it also enables a platform to produce
> multiple FMP instances to support the update
> of different regions of a FW storage device
> or update different devices that have support
> FW updates.
>
> I have put FmpDevicePkg and the new tools
> to support building capsules as RFCs to get
> some initial feedback.
>
> My next step is to add an edk2-staging branch
> with this content along with a set of complete
> examples around the MinnowMax platform that
> demonstrate the capabilities and usage.
>
> I will also create a set of Wiki pages on how
> to integrate this feature into a platform.
>

OK, that does sound rather useful.

Happy to test/prototype things as well, if that helps.


      reply	other threads:[~2018-05-31 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 22:37 [RFC v3 0/4] Add FmpDevicePkg Michael D Kinney
2018-05-29 22:37 ` [RFC v3 1/4] FmpDevicePkg: Add package, library classes, and PCDs Michael D Kinney
2018-05-29 22:37 ` [RFC v3 2/4] FmpDevicePkg: Add library instances Michael D Kinney
2018-06-04 23:09   ` Yao, Jiewen
2018-06-04 23:54     ` Kinney, Michael D
2018-05-29 22:37 ` [RFC v3 3/4] FmpDevicePkg: Add FmpDxe module Michael D Kinney
2018-05-29 22:37 ` [RFC v3 4/4] FmpDevicePkg: Add DSC file to build all package components Michael D Kinney
2018-05-30  7:08 ` [RFC v3 0/4] Add FmpDevicePkg Ard Biesheuvel
2018-05-30 15:15   ` Kinney, Michael D
2018-05-31 11:13     ` Ard Biesheuvel [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='CAKv+Gu_PNYKBU-5JOzbVPLKnuoQFV=MXB_=ziCOrqqjmk=A0tg@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