mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	"Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ong, Boon Leong" <boon.leong.ong@intel.com>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Ming Lei <ming.lei@canonical.com>
Subject: Re: [PATCH v2 3/3] efi: Capsule update with user helper interface
Date: Sat, 8 Nov 2014 13:05:56 +0000	[thread overview]
Message-ID: <20141108130556.GM3592@console-pimps.org> (raw)
In-Reply-To: <CALCETrV6M5D4iPjxPwNkMWTfVYDf3wSuZ9P23miUSR-jMGRyvg@mail.gmail.com>

On Tue, 04 Nov, at 08:35:40AM, Andy Lutomirski wrote:
> 
> Am I missing something here?  The current proposal is missing the
> success/failure part, unless you count the loaded count (in a
> different sysfs directory) as a useful interface for that.
 
As Wilson pointed out, you only get the ability to make meaningful
success/failure declarations once you've performed the reboot.

I know of no firmware that will hot-patch itself when you call
UpdateCapsule(). A reboot is always required. Certainly that's the way
Windows will work from what I've read, which means that for x86 it's
pretty much set in stone.

Which means there's only so much info you can return to userspace once
you've handed the blob to the firmware. I don't see a huge problem with
printing things in kernel buffer, since that's how other
firmware-related things work today.

-- 
Matt Fleming, Intel Open Source Technology Center

  parent reply	other threads:[~2014-11-08 13:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  3:07 [PATCH v2 0/3] Enable user helper interface for efi capsule update Kweh Hock Leong
2014-11-03  3:07 ` [PATCH v2 1/3] firmware loader: Introduce new API - request_firmware_abort() Kweh Hock Leong
2014-11-03 10:15   ` Henrique de Moraes Holschuh
2014-11-03 12:07     ` Matt Fleming
2014-11-08 19:06   ` Greg Kroah-Hartman
2014-11-13  2:51     ` Kweh, Hock Leong
2014-11-17 15:12       ` Matt Fleming
2014-11-18  6:31         ` Kweh, Hock Leong
2014-11-19  2:05           ` Greg Kroah-Hartman
2014-11-03  3:07 ` [PATCH v2 2/3] firmware loader: fix hung task warning dump Kweh Hock Leong
2014-11-08 19:07   ` Greg Kroah-Hartman
2014-11-03  3:07 ` [PATCH v2 3/3] efi: Capsule update with user helper interface Kweh Hock Leong
2014-11-04  4:32   ` Greg Kroah-Hartman
2014-11-04  5:20     ` Andy Lutomirski
2014-11-04  6:04       ` Kweh, Hock Leong
2014-11-04  6:32         ` Andy Lutomirski
2014-11-04  8:03           ` Kweh, Hock Leong
2014-11-04 14:18           ` Matt Fleming
2014-11-04 14:57             ` Andy Lutomirski
2014-11-04 15:40               ` Greg KH
2014-11-04 16:35                 ` Andy Lutomirski
2014-11-06 12:53                   ` Kweh, Hock Leong
2014-11-06 16:52                     ` Andy Lutomirski
2014-11-10  8:31                       ` Kweh, Hock Leong
2014-11-10 19:31                         ` Andy Lutomirski
2014-11-08 13:05                   ` Matt Fleming [this message]
2014-11-08 15:54                     ` Andy Lutomirski
2015-02-27  5:06   ` Roy Franz
2015-02-27 11:35     ` Kweh, Hock Leong
2014-11-03 19:33 ` [PATCH v2 0/3] Enable user helper interface for efi capsule update Andy Lutomirski
2014-11-03 21:27   ` Greg Kroah-Hartman
2014-11-03 21:32     ` Andy Lutomirski
2014-11-03 23:02       ` Greg Kroah-Hartman
2014-11-03 23:08         ` Andy Lutomirski
2014-11-04  0:38           ` Greg Kroah-Hartman
2014-11-04  1:14             ` Andy Lutomirski
2014-11-04 14:07             ` Matt Fleming
2014-11-05  9:52               ` Kweh, Hock Leong

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=20141108130556.GM3592@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=boon.leong.ong@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hock.leong.kweh@intel.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=matt.fleming@intel.com \
    --cc=ming.lei@canonical.com \
    --cc=semen.protsenko@linaro.org \
    /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

all inboxes | Powered by JetHome®