From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>, ron minnich <rminnich@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE..." <x86@kernel.org>,
coreboot <coreboot@coreboot.org>
Subject: Re: [coreboot] [PATCH] x86: add coreboot framebuffer support
Date: Sat, 06 Sep 2014 00:40:33 +0300 [thread overview]
Message-ID: <540A2DD1.1040002@gmail.com> (raw)
In-Reply-To: <540A2B9A.1070707@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On 06.09.2014 00:31, H. Peter Anvin wrote:
> On 09/05/2014 02:23 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 06.09.2014 00:18, ron minnich wrote:
>>> Vladimir can you point me to that patch? This sounds
>>> interesting.
>>>
>> https://lkml.org/lkml/2010/8/25/190
>>
>
> I believe *most* of this patch has already gotten merged as we now use
> simplefb on x86 as well. So all we need is probably the ID.
>
Yes, efifb has the same semantics. We just need some ID with clear
documentation saying sth like "implies framebuffer without anything
else" so that noone will get an idea to plug e.g. vga hooks into it.
> -hpa
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2014-09-05 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 10:25 [PATCH] x86: add coreboot framebuffer support Gerd Hoffmann
2014-09-05 20:05 ` H. Peter Anvin
2014-09-05 20:55 ` [coreboot] " ron minnich
2014-09-05 21:09 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-09-05 21:18 ` ron minnich
2014-09-05 21:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-09-05 21:31 ` H. Peter Anvin
2014-09-05 21:40 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-09-05 21:48 ` H. Peter Anvin
2014-09-09 6:15 ` Gerd Hoffmann
2014-09-05 21:20 ` 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=540A2DD1.1040002@gmail.com \
--to=phcoder@gmail.com \
--cc=coreboot@coreboot.org \
--cc=hpa@zytor.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rminnich@gmail.com \
--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