All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Matthew Garrett <mjg@redhat.com>, Olof Johansson <olof@lixom.net>,
	Peter Jones <pjones@redhat.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86: Switch to vga console only if framebuffer details are missing
Date: Mon, 17 Sep 2012 12:03:40 +0100	[thread overview]
Message-ID: <1347879820.12641.3.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20120917120047.42b520ac@pyramind.ukuu.org.uk>

On Mon, 2012-09-17 at 12:00 +0100, Alan Cox wrote:
> On Mon, 17 Sep 2012 11:29:08 +0100
> Matt Fleming <matt@console-pimps.org> wrote:
> 
> > From: Matt Fleming <matt.fleming@intel.com>
> > 
> > The efi_enabled variable has come to mean "Do we have EFI runtime
> > services available?". However, lack of EFI runtime services does not
> > mean that we should switch to using the VGA console. Provided that the
> > boot loader passed the dimensions of the EFI framebuffer there is no
> > reason we can't use efifb.
> 
> Speed is the obvious one. vga con is fast, efifb is not

Right, and that's an entirely valid reason for wanting vga con over
efifb, but in that case users should just disable the efifb driver.

-- 
Matt Fleming, Intel Open Source Technology Center


  reply	other threads:[~2012-09-17 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 10:29 [PATCH] x86: Switch to vga console only if framebuffer details are missing Matt Fleming
2012-09-17 11:00 ` Alan Cox
2012-09-17 11:03   ` Matt Fleming [this message]
2012-10-10 13:43 ` Matt Fleming
2012-10-10 14:32   ` Peter Jones

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=1347879820.12641.3.camel@mfleming-mobl1.ger.corp.intel.com \
    --to=matt@console-pimps.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mjg@redhat.com \
    --cc=olof@lixom.net \
    --cc=pjones@redhat.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.