linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Chandramouli Narayanan <mouli@linux.intel.com>,
	Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Antonino A. Daplas" <adaplas@pol.net>,
	akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] x86_64 EFI boot support: EFI frame buffer driver
Date: Thu, 9 Aug 2007 10:40:00 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708091038060.12872@anakin> (raw)
In-Reply-To: <1186647633.15539.15.camel@caritas-dev.intel.com>

On Thu, 9 Aug 2007, Huang, Ying wrote:
> Changelog between this version and previous version (v3 of x86_64 EFI
> support patch).
> 
> 1. The include files of efifb.c is cleaned up.
> 2. Make CONFIG_FB_EFI do not depend on CONFIG_EFI.

BTW, the recommended place to put changelogs (so the tools will strip
it automatically when importing your patch) is after the first `---' and
before the diffstat output

> ---

Bogus `---' :-)

> 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.
> 
> The framebuffer driver has been tested in i386 kernel and x86_64
> kernel on EFI platform.
> 
> Signed-off-by: Chandramouli Narayanan <mouli@linux.intel.com>
> Signed-off-by: Huang Ying <ying.huang@intel.com>
> 

Missing `---' ;-)

>  drivers/video/Kconfig       |   11 ++
>  drivers/video/Makefile      |    1 
>  drivers/video/efifb.c       |  232 ++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/screen_info.h |    1 
>  4 files changed, 245 insertions(+)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

      reply	other threads:[~2007-08-09  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  8:20 [PATCH 1/2] x86_64 EFI boot support: EFI frame buffer driver Huang, Ying
2007-08-09  8:40 ` Geert Uytterhoeven [this message]

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=Pine.LNX.4.64.0708091038060.12872@anakin \
    --to=geert@linux-m68k.org \
    --cc=adaplas@pol.net \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouli@linux.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).