Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761623Ab3JPUOW (ORCPT ); Wed, 16 Oct 2013 16:14:22 -0400 Received: from mga03.intel.com ([143.182.124.21]:37412 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757764Ab3JPUOV (ORCPT ); Wed, 16 Oct 2013 16:14:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.93,508,1378882800"; d="scan'208";a="412133140" Date: Wed, 16 Oct 2013 13:14:16 -0700 From: Andi Kleen To: Matt Fleming Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, Tony Luck , Seiji Aguchi , x86@kernel.org, Matt Fleming Subject: Re: [PATCH 5/5] efi: Capsule update support and pstore backend Message-ID: <20131016201416.GG7456@tassilo.jf.intel.com> References: <1381931460-6999-1-git-send-email-matt@console-pimps.org> <1381931460-6999-6-git-send-email-matt@console-pimps.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1381931460-6999-6-git-send-email-matt@console-pimps.org> 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 Content-Length: 836 Lines: 22 > + It should be noted that enabling this opton will pass a capsule > + to the firmware on every boot. Some firmware will not allow a > + user to enter the BIOS setup when a capsule has been registered > + on the previous boot. That sounds like a problem. Can this be fixed to only do it on demand? > + > + Many EFI machines have buggy implementations of the UpdateCapsule() > + runtime service. This option will enable code that may not function > + correctly with your firmware. Do we need white/black lists? Controlling such things form CONFIG is not very good. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/