From: Ingo Molnar <mingo@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Peter Jones <pjones@redhat.com>,
Matt Fleming <matt@console-pimps.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/efi: Add EFI framebuffer earlyprintk support
Date: Fri, 11 Oct 2013 08:21:59 +0200 [thread overview]
Message-ID: <20131011062159.GD4975@gmail.com> (raw)
In-Reply-To: <20131010175828.GA9065@srcf.ucam.org>
* Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Thu, Oct 10, 2013 at 07:45:21PM +0200, Ingo Molnar wrote:
>
> > Also, the main question would be, what is the typical value for
> > si->lfb_depth. 32 on almost all EFI systems? All around the map? Depends
> > on what graphics state the EFI bootloader passes us?
>
> Microsoft require that it be 32, so in practice I suspect it'll always
> be 32. [...]
Ok, cool - and it's a rare sight: Microsoft standing up against bloat and
complexity.
> [...] It's possible that Itanium decides to be different.
That would be a feature!
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-11 6:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 16:41 [PATCH] x86/efi: Add EFI framebuffer earlyprintk support Matt Fleming
2013-10-10 17:28 ` Ingo Molnar
2013-10-10 17:37 ` Peter Jones
2013-10-10 17:45 ` Ingo Molnar
2013-10-10 17:58 ` Matthew Garrett
2013-10-11 6:21 ` Ingo Molnar [this message]
2013-10-10 18:09 ` Peter Jones
2013-10-11 7:08 ` Geert Uytterhoeven
2013-10-11 14:00 ` Matt Fleming
2013-10-12 17:49 ` Ingo Molnar
2013-10-13 20:47 ` H. Peter Anvin
2013-10-14 7:57 ` Ingo Molnar
2013-10-16 9:16 ` Matt Fleming
2013-10-16 9:27 ` Ingo Molnar
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=20131011062159.GD4975@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
/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).