From: Matt Fleming <matt@codeblueprint.co.uk>
To: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: joeyli <jlee@suse.com>, Matt Fleming <matt@codeblueprint.co.uk>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@alien8.de>,
"Bryan O'Donoghue" <pure.logic@nexus-software.ie>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
"Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
Mark Salter <msalter@redhat.com>, Peter Jones <pjones@redhat.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/4] EFI capsule update support
Date: Thu, 17 Mar 2016 12:57:07 +0000 [thread overview]
Message-ID: <1458219431-24741-1-git-send-email-matt@codeblueprint.co.uk> (raw)
This is the reincarnation of the EFI capsule patches I originally
posted in 2013, plus Hock's capsule loader driver from earlier this
year. Together they provide a way for users to send capsule images to
firmware.
EFI capsules are binary blobs passed from the OS to the firmware. The
firmware then parses them and makes some decision based upon their
contents. The most common use case is to bundle a flashable firmware
image into a capsule that the firmware can use to upgrade the existing
version in the flash.
The series has been tested on the Intel Quark Galileo.
I plan on queuing this up for v4.7.
Kweh, Hock Leong (1):
efi: A misc char interface to update EFI firmware
Matt Fleming (3):
efi: Move efi_status_to_err() to drivers/firmware/efi/
efi: Capsule update support
x86/efi: Force EFI reboot to process pending capsules
arch/x86/kernel/reboot.c | 9 +
drivers/firmware/efi/Kconfig | 10 +
drivers/firmware/efi/Makefile | 3 +-
drivers/firmware/efi/capsule-loader.c | 343 ++++++++++++++++++++++++++++++++++
drivers/firmware/efi/capsule.c | 286 ++++++++++++++++++++++++++++
drivers/firmware/efi/efi.c | 33 ++++
drivers/firmware/efi/reboot.c | 12 +-
drivers/firmware/efi/vars.c | 33 ----
include/linux/efi.h | 22 +++
9 files changed, 716 insertions(+), 35 deletions(-)
create mode 100644 drivers/firmware/efi/capsule-loader.c
create mode 100644 drivers/firmware/efi/capsule.c
--
2.6.2
next reply other threads:[~2016-03-17 12:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 12:57 Matt Fleming [this message]
2016-03-17 12:57 ` [PATCH 1/4] efi: Move efi_status_to_err() to drivers/firmware/efi/ Matt Fleming
2016-03-21 9:43 ` Ard Biesheuvel
2016-03-17 12:57 ` [PATCH 2/4] efi: Capsule update support Matt Fleming
2016-03-21 10:19 ` Ard Biesheuvel
2016-03-21 20:31 ` Matt Fleming
2016-03-29 12:26 ` Matt Fleming
2016-03-29 13:50 ` Ard Biesheuvel
2016-04-05 10:09 ` Matt Fleming
2016-03-17 12:57 ` [PATCH 3/4] x86/efi: Force EFI reboot to process pending capsules Matt Fleming
2016-03-17 12:57 ` [PATCH 4/4] efi: A misc char interface to update EFI firmware Matt Fleming
2016-04-01 2:48 ` deckard
2016-04-05 9:48 ` Matt Fleming
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-all 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=1458219431-24741-1-git-send-email-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hock.leong.kweh@intel.com \
--cc=hpa@zytor.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=msalter@redhat.com \
--cc=pjones@redhat.com \
--cc=pure.logic@nexus-software.ie \
--cc=semen.protsenko@linaro.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome