From: Shea Levy <shea@shealevy.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, matt.fleming@intel.com
Subject: Re: Proposal: EFI boot stub configuration file
Date: Fri, 16 Mar 2012 17:36:16 -0400 [thread overview]
Message-ID: <4F63B250.1010200@shealevy.com> (raw)
In-Reply-To: <4F63B093.9020104@zytor.com>
On 3/16/12 5:28 PM, H. Peter Anvin wrote:
> A file in UCS-2 seems messed up.
Yeah, it seemed like a good way to let the code be dumb but upon
reflection it'd just be a confusing inefficiency.
> Otherwise, seems like a reasonable idea, with a major caveat... since
> the whole point of this is to do something when it isn't possible to
> set NVRAM variables, it would make most sense to me if the
> configuration file could be founin a specific location relative to the
> kernel image itself.
OK. I'll try both approaches to see if the code complexity is greatly
increased in the relative path case.
Cheers,
Shea
next prev parent reply other threads:[~2012-03-16 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:25 Proposal: EFI boot stub configuration file Shea Levy
2012-03-16 21:28 ` H. Peter Anvin
2012-03-16 21:36 ` Shea Levy [this message]
2012-03-16 21:32 ` Shea Levy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F63B250.1010200@shealevy.com \
--to=shea@shealevy.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.