From: ebiederm@xmission.com (Eric W. Biederman)
To: "Huang, Ying" <ying.huang@intel.com>
Cc: ak@suse.de, akpm@linux-foundation.org,
Yinghai Lu <yhlu.kernel@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@pol.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] x86_64 EFI support -v3: EFI framebuffer driver
Date: Mon, 30 Jul 2007 22:34:12 -0600 [thread overview]
Message-ID: <m1zm1dtcmz.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1185851582.23149.29.camel@caritas-dev.intel.com> (Ying Huang's message of "Tue, 31 Jul 2007 11:13:02 +0800")
"Huang, Ying" <ying.huang@intel.com> writes:
> This patch adds Graphics Output Protocol support to the kernel.
> UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and
> only Graphics Output Protocol (GOP) is produced. Therefore, the boot
> loader needs to query the UEFI firmware with appropriate Output
> Protocol and pass the video information to the kernel. As a result of
> GOP protocol, an EFI framebuffer driver is needed for displaying
> console messages. The patch adds a EFI framebuffer driver. The EFI
> frame buffer driver in this patch is based on the Intel Mac
> framebuffer driver.
>
> The ELILO bootloader takes care of passing the video information as
> appropriate for EFI firmware.
Am I correct in understanding that you are not using any of the efi
runtime service infrastructure you have built up in other patches?
So far this looks like the only useful piece of the patchset.
If this doesn't use the runtime services I don't see any point
in having them.
Eric
next prev parent reply other threads:[~2007-07-31 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 3:13 [PATCH 4/5] x86_64 EFI support -v3: EFI framebuffer driver Huang, Ying
2007-07-31 4:34 ` Eric W. Biederman [this message]
2007-07-31 6:35 ` Huang, Ying
2007-08-01 5:55 ` Antonino A. Daplas
2007-08-03 6:56 ` Huang, Ying
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=m1zm1dtcmz.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=randy.dunlap@oracle.com \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@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 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).