From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752826AbbCJM06 (ORCPT ); Tue, 10 Mar 2015 08:26:58 -0400 Received: from mail-we0-f177.google.com ([74.125.82.177]:46645 "EHLO mail-we0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752693AbbCJM0z (ORCPT ); Tue, 10 Mar 2015 08:26:55 -0400 Date: Tue, 10 Mar 2015 12:26:52 +0000 From: Matt Fleming To: Peter Jones Cc: "Kweh, Hock Leong" , Andy Lutomirski , Sam Protsenko , Ming Lei , Greg Kroah-Hartman , "Ong, Boon Leong" , LKML , "linux-efi@vger.kernel.org" Subject: Re: Re: [PATCH v2 3/3] efi: Capsule update with user helper interface Message-ID: <20150310122652.GA17573@codeblueprint.co.uk> References: <20150306213912.GA8020@fenchurch.internal.datastacks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150306213912.GA8020@fenchurch.internal.datastacks.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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