[PATCH] efifb: Update documentation to include generic EFI 1.1 andUEFI 2.0 platforms

From: Darren Hart
Date: Thu Dec 08 2011 - 14:40:14 EST


According to the Kconfig help, efifb supports EFI 1.1 and UEFI 2.0 platforms
in addition to the Intel based Macs. I have Atom development platforms that
require CONFIG_FB_EFI for kernel output to the display console. I have left
the Mac kernel parameters alone as I do not have hardware to test it.

Signed-off-by: Darren Hart <dvhart@xxxxxxxxxxxxxxx>
CC: H. Peter Anvin <hpa@xxxxxxxxx>
CC: Matt Fleming <matt.fleming@xxxxxxxxxxxxxxx>
CC: Edgar Hucek <gimli@xxxxxxxxxxxxxx>
---
Documentation/fb/efifb.txt | 12 ++++++++----
1 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/Documentation/fb/efifb.txt b/Documentation/fb/efifb.txt
index a59916c..7cb9a62 100644
--- a/Documentation/fb/efifb.txt
+++ b/Documentation/fb/efifb.txt
@@ -2,12 +2,15 @@
What is efifb?
===============

-This is a generic EFI platform driver for Intel based Apple computers.
-efifb is only for EFI booted Intel Macs.
+This is a generic EFI platform driver for Intel based Apple computers and
+platforms with EFI 1.10 or UEFI 2.0 firmware. Select CONFIG_FB_EFI to add
+support for using the EFI framebuffer as your console.

Supported Hardware
==================

+EFI 1.10 platforms
+UEFI 2.0 platforms
iMac 17"/20"
Macbook
Macbook Pro 15"/17"
@@ -16,8 +19,9 @@ MacMini
How to use it?
==============

-efifb does not have any kind of autodetection of your machine.
-You have to add the following kernel parameters in your elilo.conf:
+efifb will autodetect the framebuffer on some machines, for others
+you will have to add the appropriate kernel parameters to your boot
+loader configuration. For example:
Macbook :
video=efifb:macbook
MacMini :
--
1.7.6.4
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/