From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH v4 1/2] firmware_loader: introduce new API - request_firmware_direct_full_path() Date: Wed, 15 Apr 2015 12:18:05 +0200 Message-ID: <20150415101805.GC2282@pd.tnic> References: <1429004697-28320-1-git-send-email-hock.leong.kweh@intel.com> <1429004697-28320-2-git-send-email-hock.leong.kweh@intel.com> <20150414140806.GD5989@kroah.com> <20150414161833.GE14069@pd.tnic> <20150415101455.GB4804@codeblueprint.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20150415101455.GB4804-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Matt Fleming Cc: Andy Lutomirski , Greg Kroah-Hartman , "Kweh, Hock Leong" , Ming Lei , Ong Boon Leong , LKML , "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Sam Protsenko , Peter Jones , Roy Franz List-Id: linux-efi@vger.kernel.org On Wed, Apr 15, 2015 at 11:14:55AM +0100, Matt Fleming wrote: > Well, I haven't come across a scenario where you need a brand new > interface for getting it *out* of the kernel again. Well, how are we going to read crash data on next boot then? EFI var or what? Are we going to have a generic interface like /sys/.../capsule/... or how are we imagining this to look like? Can you give a detailed example please... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --