From: Andrew Morton <akpm@linux-foundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: rpurdie@rpsys.net, romosan@sycorax.lbl.gov,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: 2.6.21-rc2 radeon backlight
Date: Fri, 2 Mar 2007 13:58:41 -0800 [thread overview]
Message-ID: <20070302135841.fbfc1e32.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703022131310.6960@pentafluge.infradead.org>
(davem cc restored)
On Fri, 2 Mar 2007 21:41:12 +0000 (GMT)
James Simmons <jsimmons@infradead.org> wrote:
> > > > yes, if i disable the radeon backlight and use the ibm acpi module,
> > > > than the backlight works. if i enable the radeon backlight, the screen
> > > > stays dark and i can't turn it on (i tried using radeontool to control
> > > > it but nothing happened).
> > >
> > > Richard, is this actually a bug, or is it a config error or something like that?
> > >
> > > And should we track it as a post-2.6.20 regression?
> >
> > Why don't we compromise for 2.6.21 by marking the Radeon backlight
> > stuff EXPERIMENTAL until the cases where IBM ACPI works and the
> > Radeon backlight stuff does not are worked out?
>
> How about this?
>
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index b8f0a11..eb54d1f 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -679,7 +679,6 @@ config FB_NVIDIA
> depends on FB && PCI
> select I2C_ALGOBIT if FB_NVIDIA_I2C
> select I2C if FB_NVIDIA_I2C
> - select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
> select FB_MODE_HELPERS
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> @@ -708,7 +707,8 @@ config FB_NVIDIA_I2C
>
> config FB_NVIDIA_BACKLIGHT
> bool "Support for backlight control"
> - depends on FB_NVIDIA
> + depends on FB_NVIDIA && EXPERIMENTAL
> + select FB_BACKLIGHT
> default y
> help
> Say Y here if you want to control the backlight of your display.
> @@ -717,7 +717,6 @@ config FB_RIVA
> tristate "nVidia Riva support"
> depends on FB && PCI
> select FB_DDC if FB_RIVA_I2C
> - select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
> select FB_MODE_HELPERS
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> @@ -754,7 +753,8 @@ config FB_RIVA_DEBUG
>
> config FB_RIVA_BACKLIGHT
> bool "Support for backlight control"
> - depends on FB_RIVA
> + depends on FB_RIVA && EXPERIMENTAL
> + select FB_BACKLIGHT
> default y
> help
> Say Y here if you want to control the backlight of your display.
> @@ -994,7 +994,6 @@ config FB_RADEON
> tristate "ATI Radeon display support"
> depends on FB && PCI
> select FB_DDC if FB_RADEON_I2C
> - select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
> select FB_MODE_HELPERS
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> @@ -1024,7 +1023,8 @@ config FB_RADEON_I2C
>
> config FB_RADEON_BACKLIGHT
> bool "Support for backlight control"
> - depends on FB_RADEON
> + depends on FB_RADEON && EXPERIMENTAL
> + select FB_BACKLIGHT
> default y
> help
> Say Y here if you want to control the backlight of your display.
> @@ -1044,7 +1044,6 @@ config FB_ATY128
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> select FB_CFB_IMAGEBLIT
> - select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
> select FB_MACMODES if PPC_PMAC
> help
> This driver supports graphics boards with the ATI Rage128 chips.
> @@ -1056,7 +1055,8 @@ config FB_ATY128
>
> config FB_ATY128_BACKLIGHT
> bool "Support for backlight control"
> - depends on FB_ATY128
> + depends on FB_ATY128 && EXPERIMENTAL
> + select FB_BACKLIGHT
> default y
> help
> Say Y here if you want to control the backlight of your display.
> @@ -1067,7 +1067,6 @@ config FB_ATY
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> select FB_CFB_IMAGEBLIT
> - select FB_BACKLIGHT if FB_ATY_BACKLIGHT
> select FB_MACMODES if PPC
> help
> This driver supports graphics boards with the ATI Mach64 chips.
> @@ -1106,7 +1105,8 @@ config FB_ATY_GX
>
> config FB_ATY_BACKLIGHT
> bool "Support for backlight control"
> - depends on FB_ATY
> + depends on FB_ATY && EXPERIMENTAL
> + select FB_BACKLIGHT
> default y
> help
> Say Y here if you want to control the backlight of your display.
Sorry, but my confidence level on this one is very low. We've had heaps
and heaps of Kconfig-related build errors in exactly this area. I'd prefer
that a patch like this one have a lot of testing and review (and a
changelog?) before we let it near a tree.
coz I've been bitten before.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-02 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ps7uutsk.fsf@sycorax.lbl.gov>
2007-03-02 2:45 ` 2.6.21-rc2 radeon backlight Andrew Morton
2007-03-02 17:24 ` Alex Romosan
2007-03-02 20:29 ` Andrew Morton
2007-03-02 20:35 ` David Miller
2007-03-02 21:01 ` Henrique de Moraes Holschuh
2007-03-02 21:22 ` Alex Romosan
2007-03-02 21:40 ` David Miller
2007-03-02 21:41 ` James Simmons
2007-03-02 21:58 ` Andrew Morton [this message]
2007-03-02 23:40 ` [Linux-fbdev-devel] " Richard Purdie
2007-03-03 16:23 ` James Simmons
2007-03-02 23:32 ` Richard Purdie
2007-03-03 5:34 ` Alex Romosan
2007-03-03 16:06 ` James Simmons
2007-03-03 16:35 ` Richard Purdie
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=20070302135841.fbfc1e32.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
--cc=rpurdie@rpsys.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;
as well as URLs for NNTP newsgroup(s).