Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751454AbbDLIi2 (ORCPT ); Sun, 12 Apr 2015 04:38:28 -0400 Received: from mga03.intel.com ([134.134.136.65]:64142 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750794AbbDLIiQ (ORCPT ); Sun, 12 Apr 2015 04:38:16 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,564,1422950400"; d="scan'208";a="694052360" From: "Kweh, Hock Leong" To: Borislav Petkov CC: Ming Lei , Matt Fleming , Greg Kroah-Hartman , "Ong, Boon Leong" , LKML , "linux-efi@vger.kernel.org" , Sam Protsenko , Peter Jones , "Andy Lutomirski" , Roy Franz Subject: RE: [PATCH v3 0/3] Enable a capsule loader interface for user to update Thread-Topic: [PATCH v3 0/3] Enable a capsule loader interface for user to update Thread-Index: AQHQc5a9LHQZx+Eu3E+weIDNWA02oZ1Ir24w Date: Sun, 12 Apr 2015 08:38:11 +0000 Message-ID: References: <1428694844-7782-1-git-send-email-hock.leong.kweh@intel.com> <20150410135807.GH28074@pd.tnic> In-Reply-To: <20150410135807.GH28074@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.20.205] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t3C8cYVL031054 Content-Length: 1606 Lines: 45 > -----Original Message----- > From: Borislav Petkov [mailto:bp@alien8.de] > Sent: Friday, April 10, 2015 9:58 PM > > On Sat, Apr 11, 2015 at 03:40:41AM +0800, Kweh, Hock Leong wrote: > > From: "Kweh, Hock Leong" > > > > Hi Guys, > > > > This patchset is created on top of "efi: Capsule update support" patch: > > http://permalink.gmane.org/gmane.linux.kernel.efi/4837 > > > > It expose a sysfs loader interface for user to upload the capsule binary > > and calling efi_capsule_update() API to pass the binary to EFI firmware. > > What I'm missing from those 0/n mails is why we need this? What is > the problem you're trying to solve and why is Peter's userspace-only > solution not enough. > > Now I have a fairly good idea why we might/could/would need the kernel > interface but I don't believe the every reader has followed the whole > discussion. > > So please start with the Why. Try to sell it to me as best as you can. > Details will be discussed later anyway. > > Thanks. > Hi Borislav, I will make the summary, for more detail, you can refer to the threads here: - https://lkml.org/lkml/2015/3/10/418 - https://lkml.org/lkml/2015/3/10/262 Summary: - Kernel interface could provide more flexibility than just firmware updates. - For embedded small foot print devices, not all vendors are affordable to include all userland tools to their product. - Not all platform support ESRT. Regards, Wilson ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?