Subject: Re: [RFC][PATCH 1/1] x86, efi: EFI boot stub config file support
From: Matt Fleming <matt.fleming@intel.com>
To: Shea Levy <shea@shealevy.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        x86@kernel.org, Maarten Lankhorst <m.b.lankhorst@gmail.com>
In-Reply-To: <4F690314.3080601@shealevy.com>
References: <4F660313.1080301@shealevy.com> <4F660402.4040300@shealevy.com>
	 <4F690314.3080601@shealevy.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Intel Corporation (UK) Ltd. - Registered No. 1134945 - Pipers
 Way, Swindon SN3 1RJ
Date: Thu, 31 May 2012 16:41:09 +0100
Message-ID: <1338478869.13028.64.camel@mfleming-mobl1.ger.corp.intel.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1210
Lines: 28

On Tue, 2012-03-20 at 18:22 -0400, Shea Levy wrote:
> On 03/18/2012 11:49 AM, Shea Levy wrote:
> > On 3/18/12 11:45 AM, Shea Levy wrote:
> >> Hello,
> >>
> >> Inlined is a patch to have the kernel read its parameters from a
> >> config file when booted via the EFI boot stub without any parameters
> >> passed. This patch roughly follows the plan I discussed when
> >> proposing this idea, except now the file is found relative to the
> >> location of the bzImage and there is no additional check to see if
> >> image->parent_handle is NULL (despite the spec saying it will be NULL
> >> when the image was loaded by the firmware itself, it was never NULL
> >> on any of the systems I tested).
> >>
> >> Cheers,
> >> Shea Levy
> 
> I haven't yet gotten a reply to this, should I wait until after the 
> merge window and resubmit it then?

I'm wondering what use case you're catering for here that can't be
handled with efibootmgr? What problem does this patch fix?

--
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/