public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: TVKR <tresko1@gmail.com>
To: edk2-devel@lists.01.org
Subject: FMP Capsule vs PMCI PLDM FW Update binaries
Date: Fri, 15 Jun 2018 07:04:10 -0500	[thread overview]
Message-ID: <CAD+hitfPGmBHV_ZVT01BZp_XOQwukg3NHC0vX6RzD4K05A-Rsg@mail.gmail.com> (raw)

Hi,

The DMTF group is coming up with a new way to update FW on PCI devices via
BMC - DSP0267. The method expects the FW binary to carry a pre-defined
header that makes it easier for BMC to perform the necessary actions.
Currently some of the OEM/ODMs are already releasing FW payloads that can
be flashed via FMP. Additionally under certain circumstances they may also
release capsules targeting FMP for firmware updates. Now, if they need to
support this new FW update method via BMC will they end up releasing
separate binaries to do the same update - one that is compliant with PLDM
spec and the other compliant with FMP capsule? Is there a way to avoid
this? Or are the OEM/ODM expected to release bulky FW packages that contain
multiple binaries to update the same type of FW.

Thanks


                 reply	other threads:[~2018-06-15 12:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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+hitfPGmBHV_ZVT01BZp_XOQwukg3NHC0vX6RzD4K05A-Rsg@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