From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io
Cc: Doug Flick <dougflick@microsoft.com>,
"Zhang, Chao B" <chao.b.zhang@intel.com>,
Wei6 Xu <wei6.xu@intel.com>
Subject: [edk2-devel] Help getting Capsule-On-Disk working (CapsuleOnDiskLoadPei and gEdkiiPeiBootInCapsuleOnDiskModePpiGuid)
Date: Mon, 25 Nov 2024 16:44:52 -0700 [thread overview]
Message-ID: <360b56e9-36af-4678-9fb2-d8ea2976fba7@bsdio.com> (raw)
I'm trying to get capsule-on-disk support added to some firmware, and
while I can get the CoD via NVRAM method working (where fwupd-efi runs
as a boot option) I'm struggling to get the native CoD process working
where I'm expecting to be able to see a progress bar as firmware is
flashed. At the moment I see OsIndications being set correctly, but I'm
missing some driver to handle it.
Should I be using CapsuleOnDiskLoadPei? If so, where is
gEdkiiPeiBootInCapsuleOnDiskModePpiGuid supposed to get produced? I
don't see any drivers that PRODUCES it - is each platform supposed to
implement it?
I'm working on an AArch64 system where I'm pretty sure memory isn't
retained between reboots so Capsule-In-Memory won't work.
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120839): https://edk2.groups.io/g/devel/message/120839
Mute This Topic: https://groups.io/mt/109781919/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2024-11-25 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 23:44 Rebecca Cran [this message]
2024-11-26 1:10 ` [edk2-devel] Help getting Capsule-On-Disk working (CapsuleOnDiskLoadPei and gEdkiiPeiBootInCapsuleOnDiskModePpiGuid) Xu, Wei6 via groups.io
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=360b56e9-36af-4678-9fb2-d8ea2976fba7@bsdio.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