linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: Matt Fleming <matt@console-pimps.org>,
	Josh Triplett <josh@joshtriplett.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Bryan O'Donoghue" <bryan.odonoghue.lkml@nexus-software.ie>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Josh Boyer <jwboyer@redhat.com>
Subject: Re: [PATCH] Remove warning in efi_enter_virtual_mode
Date: Thu, 18 Apr 2013 13:11:18 -0700	[thread overview]
Message-ID: <51705366.8070001@intel.com> (raw)
In-Reply-To: <1366315083.13667.19.camel@x230.lan>

On 04/18/2013 12:58 PM, Matthew Garrett wrote:
> On Thu, 2013-04-18 at 20:55 +0100, Matt Fleming wrote:
> 
>> If there are machines out there that would require us to write support,
>> it's probably worth doing now instead of punting. But it sounds like
>> there aren't any.
> 
> I would expect that if there are any 32-bit UEFI systems that ship with
> BGRT support (and Darren makes it sound like that's a possibility),
> there's a realistic chance of the BGRT ending up allocated above the
> highmem barrier.

I can certainly ensure we sit below that barrier on the MinnowBoard. We
can also speak with the Intel UEFI firmware development teams to see
about making that a requirement. I don't know if we'll be successful,
but Matt, Peter, and I have recently coaxed some changes of that nature in.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

  reply	other threads:[~2013-04-18 20:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 15:58 [PATCH] Remove warning in efi_enter_virtual_mode Bryan O'Donoghue
2013-04-17 14:06 ` Matt Fleming
2013-04-17 22:00   ` Bryan O'Donoghue
2013-04-18 11:00     ` Matt Fleming
2013-04-18 13:40       ` Josh Boyer
2013-04-18 15:01         ` Matthew Garrett
2013-04-18 15:17           ` Josh Boyer
2013-04-18 14:51       ` Darren Hart
2013-04-18 16:19         ` Matt Fleming
2013-04-19  0:18           ` Darren Hart
2013-04-19  7:50             ` Matt Fleming
2013-04-19 12:01               ` Josh Boyer
2013-09-10 17:43               ` Darren Hart
2013-09-12  7:55                 ` Matt Fleming
2013-09-12 22:30                   ` Darren Hart
2013-04-18 16:33       ` Josh Triplett
2013-04-18 16:38         ` H. Peter Anvin
2013-04-18 16:44           ` Josh Triplett
2013-04-18 19:55             ` Matt Fleming
2013-04-18 19:57               ` H. Peter Anvin
2013-04-18 19:58               ` Matthew Garrett
2013-04-18 20:11                 ` Darren Hart [this message]
2013-04-18 20:13                   ` H. Peter Anvin
2013-04-18 20:17                     ` Darren Hart
2013-04-18 20:45                       ` H. Peter Anvin
2013-04-18 22:07       ` Bryan O'Donoghue
2013-04-18 23:01         ` Josh Triplett
2013-04-18 23:44           ` H. Peter Anvin
2013-04-18 23:42         ` H. Peter Anvin

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=51705366.8070001@intel.com \
    --to=darren.hart@intel.com \
    --cc=bryan.odonoghue.lkml@nexus-software.ie \
    --cc=hpa@zytor.com \
    --cc=josh@joshtriplett.org \
    --cc=jwboyer@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=matthew.garrett@nebula.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).