From: Adrian Bunk <bunk@stusta.de>
To: James Simmons <jsimmons@infradead.org>,
"Antonino A. Daplas" <adaplas@pol.net>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC: 2.6.22 patch] don't offer DISPLAY_SUPPORT for now
Date: Fri, 22 Jun 2007 01:52:04 +0200 [thread overview]
Message-ID: <20070621235204.GF23017@stusta.de> (raw)
DISPLAY_SUPPORT offers support code without any users currently in the
tree. For a user it's quite confusing that the help text talks about
"proper drivers" when none are available.
This patch therefore lets DISPLAY_SUPPORT depend on BROKEN until there
will be user.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
--- linux-2.6.22-rc4-mm2/drivers/video/display/Kconfig.old 2007-06-21 18:41:26.000000000 +0200
+++ linux-2.6.22-rc4-mm2/drivers/video/display/Kconfig 2007-06-21 18:41:41.000000000 +0200
@@ -1,24 +1,25 @@
#
# Display drivers configuration
#
menu "Display device support"
config DISPLAY_SUPPORT
tristate "Display panel/monitor support"
+ depends on BROKEN # lacks users
---help---
This framework adds support for low-level control of a display.
This includes support for power.
Enable this to be able to choose the drivers for controlling the
physical display panel/monitor on some platforms. This not only
covers LCD displays for PDAs but also other types of displays
such as CRT, TVout etc.
To have support for your specific display panel you will have to
select the proper drivers which depend on this option.
comment "Display hardware drivers"
depends on DISPLAY_SUPPORT
endmenu
next reply other threads:[~2007-06-21 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 23:52 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-01 20:21 [RFC: 2.6.22 patch] don't offer DISPLAY_SUPPORT for now Adrian Bunk
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=20070621235204.GF23017@stusta.de \
--to=bunk@stusta.de \
--cc=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.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