From: "H. Peter Anvin" <hpa@zytor.com>
To: spock@gentoo.org
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, krzysztof.h1@poczta.fm,
Andrew Morton <akpm@linux-foundation.org>,
bonbons@linux-vserver.org
Subject: Re: [PATCH v2] fbdev: ignore VESA modes if framebuffer does not support them
Date: Thu, 25 Sep 2008 02:12:48 -0700 [thread overview]
Message-ID: <48DB5610.4020208@zytor.com> (raw)
In-Reply-To: <20080924190832.GA19141@spock.one.pl>
Michal Januszewski wrote:
> Currently, it is possible to set a graphics VESA mode at boot time via
> the vga= parameter even when no framebuffer driver supporting this is
> configured. This could lead to the system booting with a black screen,
> without a usable console.
> diff --git a/include/linux/screen_info.h b/include/linux/screen_info.h
> index 1ee2c05..20fdc2f 100644
> --- a/include/linux/screen_info.h
> +++ b/include/linux/screen_info.h
> @@ -76,6 +76,10 @@ extern struct screen_info screen_info;
> #define ORIG_VIDEO_LINES (screen_info.orig_video_lines)
> #define ORIG_VIDEO_ISVGA (screen_info.orig_video_isVGA)
> #define ORIG_VIDEO_POINTS (screen_info.orig_video_points)
> +
> +#define FB_SUPPORTS_BOOT_VESA (defined(CONFIG_FB_VESA) || \
> + defined(CONFIG_FB_SIS) || defined(CONFIG_FB_IMAC) || \
> + defined(CONFIG_FB_INTEL))
> #endif /* __KERNEL__ */
>
> #endif /* _SCREEN_INFO_H */
I'm *REALLY* skeptical to burying this in screen_info like this, it
would probably be better to put it in Kconfig, or it is unlikely to get
updated properly.
-hpa
prev parent reply other threads:[~2008-09-25 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 19:08 [PATCH v2] fbdev: ignore VESA modes if framebuffer does not support them Michal Januszewski
2008-09-25 9:12 ` H. Peter Anvin [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=48DB5610.4020208@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bonbons@linux-vserver.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.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 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.