From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Revisiting EFI boot stub config file support Date: Wed, 02 Jan 2013 09:52:27 -0800 Message-ID: <50E473DB.4050504@zytor.com> References: <50E306FB.6080607@shealevy.com> <50E31BB4.7040702@zytor.com> <710F73BE-9F65-48C9-8739-BFCF097F4B07@shealevy.com> <20130102174319.GA2590@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130102174319.GA2590@srcf.ucam.org> Sender: linux-kernel-owner@vger.kernel.org To: Matthew Garrett Cc: Shea Levy , "linux-efi@vger.kernel.org" , Linux Kernel Mailing List List-Id: linux-efi@vger.kernel.org On 01/02/2013 09:43 AM, Matthew Garrett wrote: > On Wed, Jan 02, 2013 at 08:26:29AM -0500, Shea Levy wrote: > >> Hm, ok. Does the boot stub have access to CONFIG_CMDLINE? Or could >> another compile-time setting be added so that distros can ship livecds >> that automatically use a config file found at a hard-coded location? > > Just pass the config file as the first argument? > CONFIG_CMDLINE can certainly become available to the stub... it's a compile-time constant. -hpa