From: Peter Jones <pjones@redhat.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Colin Watson <cjwatson@canonical.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] Add new linearfb driver
Date: Wed, 25 Aug 2010 13:24:01 -0400 [thread overview]
Message-ID: <4C7551B1.3000703@redhat.com> (raw)
In-Reply-To: <20100825190438.55ecb34d@neptune.home>
On 08/25/2010 01:04 PM, Bruno Prémont wrote:
> On Wed, 25 August 2010 Colin Watson <cjwatson@canonical.com> wrote:
>> Split out linearfb from efifb so that boot loaders can program it as a
>> simple linear framebuffer on non-EFI systems. This is useful for boot
>> loaders with their own graphics drivers, e.g. GRUB 2, since in some
>> cases on x86 they can set up non-VESA modes and thus can't program
>> vesafb.
>>
>> efifb is reworked on top of this common code, and it should be possible
>> to do the same with some other framebuffer drivers in future.
>>
>> Signed-off-by: Colin Watson <cjwatson@canonical.com>
>> Acked-by: Matthew Garrett <mjg@redhat.com>
>> Cc: Peter Jones <pjones@redhat.com>
>> ---
>> drivers/video/Kconfig | 17 ++-
>> drivers/video/Makefile | 1 +
>> drivers/video/efifb.c | 222 +----------------------------
>> drivers/video/linearfb.c | 332 +++++++++++++++++++++++++++++++++++++++++++
>> include/linux/fb.h | 8 +
>> include/linux/screen_info.h | 2 +
>> 6 files changed, 364 insertions(+), 218 deletions(-)
>> create mode 100644 drivers/video/linearfb.c
>>
>> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
>> index 59c51d9..a7735ec 100644
>> --- a/drivers/video/Kconfig
>> +++ b/drivers/video/Kconfig
>> @@ -721,13 +721,24 @@ config FB_VESA
>> You will get a boot time penguin logo at no additional cost. Please
>> read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
>>
>> -config FB_EFI
>> - bool "EFI-based Framebuffer Support"
>> - depends on (FB = y) && X86 && EFI
>> +config FB_LINEAR
>> + bool "Simple linear framebuffer support"
>> + depends on FB
>> select FB_CFB_FILLRECT
>> select FB_CFB_COPYAREA
>> select FB_CFB_IMAGEBLIT
> ^^^^^^^^^^^^^^^^^^^^^^^
>
>> help
>> + This is a simple linear frame buffer device driver. It has no
>> + hardware-specific programming capability, but must be programmed
>> + by the boot loader or by another frame buffer driver.
>> +
>> + If unsure, say N.
>> +
>> +config FB_EFI
>> + bool "EFI-based Framebuffer Support"
>> + depends on (FB = y) && X86 && EFI
>> + select FB_LINEAR
> ^^^^^^^^^^^^^^^^
> Has kconfig been adjusted to process select recursively?
> If not the selects from FB_LINEAR will have to be copied here.
This could also be solved by just making it depend on FB_LINEAR instead of
using "select".
--
Peter
I number the Linux folks among my personal heroes.
-- Donald Knuth
01234567890123456789012345678901234567890123456789012345678901234567890123456789
next prev parent reply other threads:[~2010-08-25 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 14:11 [PATCH] Add new linearfb driver Colin Watson
2010-08-25 15:03 ` Peter Jones
2010-08-25 17:04 ` Bruno Prémont
2010-08-25 17:24 ` Peter Jones [this message]
2010-08-25 17:28 ` Colin Watson
2010-08-25 20:22 ` Geert Uytterhoeven
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=4C7551B1.3000703@redhat.com \
--to=pjones@redhat.com \
--cc=bonbons@linux-vserver.org \
--cc=cjwatson@canonical.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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