From: "Chen, Kenji" <kenji.chen@intel.com>
To: Sean <sean.brogan@microsoft.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Patch for Bug 2236 on Bugzilla
Date: Mon, 14 Oct 2019 03:52:30 +0000 [thread overview]
Message-ID: <BN8PR11MB37467FEC6EF0C2406130334C82900@BN8PR11MB3746.namprd11.prod.outlook.com> (raw)
In-Reply-To: <26543.1570688887718268129@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
NIST 800-193 needs FW Resiliency support. It is to ensure the FW update is healthy and has a way to roll back to previous version if there was a bad update. If LSV is changed whenever the update is accomplished (health is not sure), there will be some difficulties to handle LSV when the update is judged as unhealth update by platform sides. Platform would roll back the update but has no way to roll back the LSV brought by the capsule. So, next attempt (maybe healthy one) would be blocked if the roll-backed image brought LSV equals the version of roll-backed image.
From: sean.brogan via [] <sean.brogan=microsoft.com@[]>
Sent: Thursday, October 10, 2019 2:28 PM
To: Chen; Chen, Kenji <kenji.chen@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] Patch for Bug 2236 on Bugzilla
Since the LSV can be managed from within the FmpDeviceLib i don't understand why this change is required. This adds yet again more complexity to all users of FmpDxe for a very niche use case. I believe the hooks already exist that would allow you to achieve the same functionality from within your own FmpDeviceLib.
Thanks
Sean
[-- Attachment #2: Type: text/html, Size: 3812 bytes --]
prev parent reply other threads:[~2019-10-14 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:59 Patch for Bug 2236 on Bugzilla Chen, Kenji
2019-10-09 13:37 ` Liming Gao
2019-10-09 16:12 ` Chen, Kenji
2019-10-09 16:44 ` Chen, Kenji
2019-10-10 6:28 ` [edk2-devel] " Sean
2019-10-14 3:52 ` Chen, Kenji [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=BN8PR11MB37467FEC6EF0C2406130334C82900@BN8PR11MB3746.namprd11.prod.outlook.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