From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Michael D Kinney <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Eric Dong <eric.dong@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Star Zeng <star.zeng@intel.com>, David Wei <david.wei@intel.com>
Subject: Re: [Patch v3 0/3] Add DisplayUpdateProgressLib for capsules
Date: Tue, 29 May 2018 11:51:51 +0200 [thread overview]
Message-ID: <CAKv+Gu_qKe4hzaFeLoJaupOQa6TSV5e-UHF7bw89ce+BVAooCw@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu9SBLJTSheOk23T4Akq_ys6bsRipWL6UdJm1cnn2zeaRg@mail.gmail.com>
On 29 May 2018 at 11:51, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 25 May 2018 at 08:15, Michael D Kinney <michael.d.kinney@intel.com> wrote:
>> https://bugzilla.tianocore.org/show_bug.cgi?id=801
>>
>> Based on content from:
>>
>> https://github.com/Microsoft/MS_UEFI/blob/share/MsCapsuleSupport/MsCapsuleUpdatePkg/Include/Library/DisplayUpdateProgressLib.h
>> https://github.com/Microsoft/MS_UEFI/tree/share/MsCapsuleSupport/MsCapsuleUpdatePkg/Library/DisplayUpdateProgressGraphicsLib
>> https://github.com/Microsoft/MS_UEFI/tree/share/MsCapsuleSupport/MsCapsuleUpdatePkg/Library/DisplayUpdateProgressTextLib
>>
>> Updates for V3
>> ==============
>> * Add Version field to EDKII_FIRMWARE_MANAGEMENT_PROGRESS_PROTOCOL
>> * Break up patch series into 4 smaller patch series to handle dependencies
>> between the edk2 repository and the edk2-platforms repository.
>> + Patch series for edk2 repo that adds DisplayUpdateProgressLib class and
>> instances. Defines the EDKII_FIRMWARE_MANAGEMENT_PROGRESS_PROTOCOL.
>> Adds PerformFlashWriteWithProgress() API to the PlatformFlashAccessLib.
>> + Patch series for platforms in edk2-platforms that use capsules to add the
>> DisplayUpdateProgressLib mapping to the DSC files and add the
>> PerformFlashWriteWithProgress() API implementation to the
>> PlatformFlashAccessLib implementations.
>> + Patch series for platforms in edk2 that use capsules to add the
>> DisplayUpdateProgressLib mapping to the DSC files and add the
>> PerformFlashWriteWithProgress() API implementation to the
>> PlatformFlashAccessLib implementations.
>> + Patch for edk2 that adds the use of the DisplayUpateProgressLib and the
>> PerformFlashWriteWithProgress() API .
>>
>> Updates for V2
>> ==============
>> * Change DisplayUpdateProgressGraphicsLib to DisplayUpdateProgressLibGraphics
>> * Change DisplayUpdateProgressTextLib to DisplayUpdateProgressLibText
>> * Clarify that color in Firmware Management Progress Protocol is the foreground color
>> * Add missing parameters to PerformFlashWriteWithProgress() function header.
>> * Update PerformFlashWriteWithProgress() function header describing the use of
>> the start and end percentage values.
>> * Update QuarkPlatformPkg PerformFlashWriteWithProgress() to call Progress() for
>> the end precentage.
>> * Update Vlv2Tbl2DevicePkg PerformFlashWriteWithProgress() to call Progress()
>> for the end precentage.
>>
>> Add DisplayUpdateProgressLib class along implementations for both graphical
>> (Graphics Output Protocol based) and text (Simple Text Output Protocol based)
>> consoles. Also add the EDK II Firmware Management Progress Protocol that is an
>> optional protocol that provides the progress bar color and a watchdog timeout
>> value thaty can be used when a firmware image is updated in a firmware device.
>>
>> * Add progress support to DxeCapsuleLibFmp
>> * Add progress support to SystemFirmwareUpdateDxe
>> * Add progress support to PlatformFlashAccessLib class and instances.
>> * Reduce Print() calls during a firmware update.
>>
>> Cc: Sean Brogan <sean.brogan@microsoft.com>
>> Cc: Star Zeng <star.zeng@intel.com>
>> Cc: Eric Dong <eric.dong@intel.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>> Cc: David Wei <david.wei@intel.com>
>> Cc: Mang Guo <mang.guo@intel.com>
>> Cc: Kelly Steele <kelly.steele@intel.com>
>>
>> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>>
>> Michael D Kinney (3):
>> MdeModulePkg: Add DisplayUpdateProgressLib class
>> MdeModulePkg: Add DisplayUpdateProgressLib instances
>> SignedCapsulePkg/PlatformFlashAccessLib: Add progress API
>>
>
> This message says 0/3, but there appear to be 4 patches in the series???
>
Never mind, the threading in my email client confused me.
next prev parent reply other threads:[~2018-05-29 9:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 6:15 [Patch v3 0/3] Add DisplayUpdateProgressLib for capsules Michael D Kinney
2018-05-25 6:15 ` [Patch v3 1/3] MdeModulePkg: Add DisplayUpdateProgressLib class Michael D Kinney
2018-05-25 11:06 ` Zeng, Star
2018-05-25 6:15 ` [Patch v3 2/3] MdeModulePkg: Add DisplayUpdateProgressLib instances Michael D Kinney
2018-05-25 11:10 ` Zeng, Star
2018-05-31 11:09 ` Ard Biesheuvel
2018-06-04 20:24 ` Kinney, Michael D
2018-05-25 6:15 ` [Patch v3 3/3] SignedCapsulePkg/PlatformFlashAccessLib: Add progress API Michael D Kinney
2018-05-28 19:18 ` Yao, Jiewen
2018-05-28 19:07 ` [Patch v3 0/3] Add DisplayUpdateProgressLib for capsules Yao, Jiewen
2018-05-29 9:51 ` Ard Biesheuvel
2018-05-29 9:51 ` Ard Biesheuvel [this message]
2018-05-29 12:43 ` Ard Biesheuvel
2018-05-29 13:05 ` Gao, Liming
2018-05-29 13:08 ` Ard Biesheuvel
2018-05-29 14:31 ` Kinney, Michael D
2018-05-31 11:12 ` Ard Biesheuvel
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_qKe4hzaFeLoJaupOQa6TSV5e-UHF7bw89ce+BVAooCw@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