From: Peter Jones <pjones@redhat.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
"lkml," <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Edgar Hucek <gimli@dark-green.com>
Subject: Re: [PATCH] efifb: Update documentation to include generic EFI 1.1 and UEFI 2.0 platforms
Date: Thu, 08 Dec 2011 15:37:03 -0500 [thread overview]
Message-ID: <4EE11FEF.2060003@redhat.com> (raw)
In-Reply-To: <1323374061.3894.81.camel@mfleming-mobl1.ger.corp.intel.com>
On 12/08/2011 02:54 PM, Matt Fleming wrote:
> (Adding Peter Jones, the efifb maintainer)
>
> On Thu, 2011-12-08 at 11:40 -0800, Darren Hart wrote:
>> 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@linux.intel.com>
>> CC: H. Peter Anvin<hpa@zytor.com>
>> CC: Matt Fleming<matt.fleming@linux.intel.com>
>> CC: Edgar Hucek<gimli@dark-green.com>
>> ---
>> 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
>
> Looks good to me,
>
> Acked-by: Matt Fleming<matt.fleming@intel.com>
Likewise:
Acked-by: Peter Jones <pjones@redhat.com>
--
Peter
Space, is big. Really big. You just won't believe how vastly hugely
mindbogglingly big it is. I mean you may think it's a long way down the
road to the chemist, but that's just peanuts to space.
-- The Hitchhiker's Guide to the Galaxy
01234567890123456789012345678901234567890123456789012345678901234567890123456789
next prev parent reply other threads:[~2011-12-08 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 19:40 [PATCH] efifb: Update documentation to include generic EFI 1.1 and UEFI 2.0 platforms Darren Hart
2011-12-08 19:54 ` Matt Fleming
2011-12-08 20:37 ` Peter Jones [this message]
2011-12-10 19:40 ` gimli
2011-12-11 9:24 ` Darren Hart
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=4EE11FEF.2060003@redhat.com \
--to=pjones@redhat.com \
--cc=dvhart@linux.intel.com \
--cc=gimli@dark-green.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.