linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Peter Jones <pjones@redhat.com>
Cc: "Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	Ming Lei <ming.lei@canonical.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Ong, Boon Leong" <boon.leong.ong@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>
Subject: Re: Re: [PATCH v2 3/3] efi: Capsule update with user helper interface
Date: Tue, 10 Mar 2015 12:26:52 +0000	[thread overview]
Message-ID: <20150310122652.GA17573@codeblueprint.co.uk> (raw)
In-Reply-To: <20150306213912.GA8020@fenchurch.internal.datastacks.com>

On Fri, 06 Mar, at 04:39:12PM, Peter Jones wrote:
> 
> So again: do we really need or want to do this?

One thing that we totally lose the ability to do is use the capsule
interface for things *other* than firmware updates, e.g.

 https://lkml.org/lkml/2013/10/16/327 

Also, requiring embedded or custom OS to include fwupdate into their
existing boot solutions is a bit heavy handed when literally all they
want to do is cat a binary blob to a sysfs file.

I don't see why we can't have both solutions.

Another thing is that ESRT isn't going to be supported by every
platform.

So, for the sysfs interface, let's not allow loading from /lib. Let's
not require a userland tool. Let's just do,

  # echo /path/to/my/awesome/capsule.bin > /sys/../capsule

and be done with it.

Hmmm?

-- 
Matt Fleming, Intel Open Source Technology Center

  parent reply	other threads:[~2015-03-10 12:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F54AEECA5E2B9541821D670476DAE19C2B8AC95C@PGSMSX102.gar.corp.intel.com>
2015-02-24 12:49 ` Re: [PATCH v2 3/3] efi: Capsule update with user helper interface Kweh, Hock Leong
2015-02-25 11:47   ` Borislav Petkov
2015-02-25 12:38     ` Kweh, Hock Leong
2015-02-25 12:49       ` Borislav Petkov
2015-02-26 15:30     ` Andy Lutomirski
2015-02-26 15:54       ` Borislav Petkov
2015-03-02 11:24         ` Matt Fleming
2015-03-06 21:39   ` Peter Jones
2015-03-06 21:49     ` Roy Franz
2015-03-06 22:17       ` Peter Jones
2015-03-10 12:26     ` Matt Fleming [this message]
2015-03-10 15:21       ` Peter Jones
2015-03-10 15:26         ` Andy Lutomirski
2015-03-10 15:40           ` Peter Jones
2015-03-10 15:51             ` Andy Lutomirski
2015-03-10 17:26               ` Peter Jones
2015-03-10 17:31                 ` Andy Lutomirski
2015-03-12 22:47               ` Matt Fleming
2015-03-13 14:42                 ` Greg Kroah-Hartman
2015-03-16 15:35                   ` Andy Lutomirski
2015-03-02 10:59 Kweh, Hock Leong
2015-03-02 12:29 ` Matt Fleming
2015-03-03  5:56   ` Kweh, Hock Leong
2015-03-03 20:37     ` Andy Lutomirski
2015-03-03 20:49       ` Borislav Petkov
2015-03-03 21:56         ` Andy Lutomirski
2015-03-05  9:18       ` Kweh, Hock Leong
2015-03-05 23:08         ` Andy Lutomirski
2015-03-06  8:13           ` Borislav Petkov
2015-03-06 11:41             ` Kweh, Hock Leong
2015-03-06 14:47               ` Borislav Petkov
2015-03-06 12:20           ` Kweh, Hock Leong
2015-03-06 19:05             ` Andy Lutomirski

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=20150310122652.GA17573@codeblueprint.co.uk \
    --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=ming.lei@canonical.com \
    --cc=pjones@redhat.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;
as well as URLs for NNTP newsgroup(s).