linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Werner,
	Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>,
	Lemberg <wl@gnu.org>
Subject: Re: [PATCH] fbdev: does not allow VESA modes without compiled-in drivers (bug #13249)
Date: Tue, 26 May 2009 23:15:16 -0700	[thread overview]
Message-ID: <20090526231516.b0cf789f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090520142704.0de8aa81.krzysztof.h1@poczta.fm>

On Wed, 20 May 2009 14:27:04 +0200 Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:

> From: Krzysztof Helt <krzysztof.h1@wp.pl>
> 
> Does not allow to accept VESA modes by the "vga=" kernel parameter
> if there is no frame buffer driver compiled-in to handle it.
> 
> Bug was reported by Werner Lemberg as kernel bug #13249
> "Intel 945GM: Boot option`vga=0x31a' breaks display of TTYs".
> 
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
> ---
> 
> Werner, please test it. It should produce a correct display
> with intelfb compiled in (=y) and as a module (=m).
> 
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 0048f11..c787357 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -1122,7 +1122,7 @@ config FB_INTEL
>  	select FB_CFB_FILLRECT
>  	select FB_CFB_COPYAREA
>  	select FB_CFB_IMAGEBLIT
> -	select FB_BOOT_VESA_SUPPORT
> +	select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
>  	help
>  	  This driver supports the on-board graphics built in to the Intel
>            830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
> @@ -1460,7 +1460,7 @@ config FB_SIS
>  	select FB_CFB_FILLRECT
>  	select FB_CFB_COPYAREA
>  	select FB_CFB_IMAGEBLIT
> -	select FB_BOOT_VESA_SUPPORT
> +	select FB_BOOT_VESA_SUPPORT if FB_SIS = y
>  	help
>  	  This is the frame buffer device driver for the SiS 300, 315, 330
>  	  and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.

I read through http://bugzilla.kernel.org/show_bug.cgi?id=13249 and am
now unsure what to do with this patch?



------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 

       reply	other threads:[~2009-05-27  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090520142704.0de8aa81.krzysztof.h1@poczta.fm>
2009-05-27  6:15 ` Andrew Morton [this message]
2009-05-27  7:41 [PATCH] fbdev: does not allow VESA modes without compiled-in drivers (bug #13249) krzysztof.h1
  -- strict thread matches above, loose matches on Subject: below --
2009-06-18 21:13 Krzysztof Helt

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=20090526231516.b0cf789f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=krzysztof.h1@poczta.fm \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=wl@gnu.org \
    /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).