From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
ak@suse.de, discuss@x86-64.org, thomas@winischhofer.net
Subject: [2.6 patch] cleanup the CONFIG_VIDEO_SELECT mess
Date: Sat, 15 Apr 2006 13:56:16 +0200 [thread overview]
Message-ID: <20060415115616.GE15022@stusta.de> (raw)
We had three (sic) VIDEO_SELECT options:
- two in drivers/video/Kconfig
- one in drivers/video/console/Kconfig
This patch removes the two options in drivers/video/Kconfig and also
removes the unneeded usage in drivers/video/sis/sis_main.c .
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
drivers/video/Kconfig | 11 -----------
drivers/video/sis/sis_main.c | 2 +-
2 files changed, 1 insertion(+), 12 deletions(-)
--- linux-2.6.17-rc1-mm2-full/drivers/video/Kconfig.old 2006-04-15 13:37:49.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/drivers/video/Kconfig 2006-04-15 13:38:07.000000000 +0200
@@ -481,11 +481,6 @@
You will get a boot time penguin logo at no additional cost. Please
read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
-config VIDEO_SELECT
- bool
- depends on FB_VESA
- default y
-
config FB_HGA
tristate "Hercules mono graphics support"
depends on FB && X86
@@ -508,12 +503,6 @@
This will compile the Hercules mono graphics with
acceleration functions.
-
-config VIDEO_SELECT
- bool
- depends on (FB = y) && X86
- default y
-
config FB_SGIVW
tristate "SGI Visual Workstation framebuffer support"
depends on FB && X86_VISWS
--- linux-2.6.17-rc1-mm2-full/drivers/video/sis/sis_main.c.old 2006-04-15 13:38:41.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/drivers/video/sis/sis_main.c 2006-04-15 13:39:13.000000000 +0200
@@ -275,7 +275,7 @@
static void __devinit
sisfb_get_vga_mode_from_kernel(void)
{
-#if (defined(__i386__) || defined(__x86_64__)) && defined(CONFIG_VIDEO_SELECT)
+#ifdef CONFIG_X86
char mymode[32];
int mydepth = screen_info.lfb_depth;
reply other threads:[~2006-04-15 11:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060415115616.GE15022@stusta.de \
--to=bunk@stusta.de \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@winischhofer.net \
/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