From: Richard Purdie <rpurdie@rpsys.net>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Nvidiafb broken in 2.6.21-rc1
Date: Mon, 26 Feb 2007 10:02:01 +0000 [thread overview]
Message-ID: <1172484121.5824.1.camel@localhost.localdomain> (raw)
In-Reply-To: <jezm737pxc.fsf@sykes.suse.de>
On Sat, 2007-02-24 at 12:31 +0100, Andreas Schwab wrote:
> With 2.6.21-rc1 I get no video signal from nvidiafb on PowerMac G5.
> Bisection has identified this patch:
>
> commit 599a52d12629394236d785615808845823875868
> Author: Richard Purdie <rpurdie@rpsys.net>
> Date: Sat Feb 10 23:07:48 2007 +0000
>
> backlight: Separate backlight properties from backlight ops pointers
>
> Per device data such as brightness belongs to the indivdual device
> and should therefore be separate from the the backlight operation
> function pointers. This patch splits the two types of data and
> allows simplifcation of some code.
>
> Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Thanks, I think I know what the problem is. Could you try this change
please:
diff --git a/drivers/video/nvidia/nv_backlight.c b/drivers/video/nvidia/nv_backlight.c
index b7016e9..a50b303 100644
--- a/drivers/video/nvidia/nv_backlight.c
+++ b/drivers/video/nvidia/nv_backlight.c
@@ -23,8 +23,6 @@
#define MAX_LEVEL 0x534
#define LEVEL_STEP ((MAX_LEVEL - MIN_LEVEL) / FB_BACKLIGHT_MAX)
-static struct backlight_properties nvidia_bl_data;
-
static int nvidia_bl_get_level_brightness(struct nvidia_par *par,
int level)
{
@@ -119,7 +117,7 @@ void nvidia_bl_init(struct nvidia_par *par)
0x534 * FB_BACKLIGHT_MAX / MAX_LEVEL);
bd->props.max_brightness = FB_BACKLIGHT_LEVELS - 1;
- bd->props.brightness = nvidia_bl_data.max_brightness;
+ bd->props.brightness = bd->props.max_brightness;
bd->props.power = FB_BLANK_UNBLANK;
backlight_update_status(bd);
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <rpurdie@rpsys.net>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Nvidiafb broken in 2.6.21-rc1
Date: Mon, 26 Feb 2007 10:02:01 +0000 [thread overview]
Message-ID: <1172484121.5824.1.camel@localhost.localdomain> (raw)
In-Reply-To: <jezm737pxc.fsf@sykes.suse.de>
On Sat, 2007-02-24 at 12:31 +0100, Andreas Schwab wrote:
> With 2.6.21-rc1 I get no video signal from nvidiafb on PowerMac G5.
> Bisection has identified this patch:
>
> commit 599a52d12629394236d785615808845823875868
> Author: Richard Purdie <rpurdie@rpsys.net>
> Date: Sat Feb 10 23:07:48 2007 +0000
>
> backlight: Separate backlight properties from backlight ops pointers
>
> Per device data such as brightness belongs to the indivdual device
> and should therefore be separate from the the backlight operation
> function pointers. This patch splits the two types of data and
> allows simplifcation of some code.
>
> Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Thanks, I think I know what the problem is. Could you try this change
please:
diff --git a/drivers/video/nvidia/nv_backlight.c b/drivers/video/nvidia/nv_backlight.c
index b7016e9..a50b303 100644
--- a/drivers/video/nvidia/nv_backlight.c
+++ b/drivers/video/nvidia/nv_backlight.c
@@ -23,8 +23,6 @@
#define MAX_LEVEL 0x534
#define LEVEL_STEP ((MAX_LEVEL - MIN_LEVEL) / FB_BACKLIGHT_MAX)
-static struct backlight_properties nvidia_bl_data;
-
static int nvidia_bl_get_level_brightness(struct nvidia_par *par,
int level)
{
@@ -119,7 +117,7 @@ void nvidia_bl_init(struct nvidia_par *par)
0x534 * FB_BACKLIGHT_MAX / MAX_LEVEL);
bd->props.max_brightness = FB_BACKLIGHT_LEVELS - 1;
- bd->props.brightness = nvidia_bl_data.max_brightness;
+ bd->props.brightness = bd->props.max_brightness;
bd->props.power = FB_BLANK_UNBLANK;
backlight_update_status(bd);
next prev parent reply other threads:[~2007-02-26 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 11:31 Nvidiafb broken in 2.6.21-rc1 Andreas Schwab
2007-02-24 11:31 ` Andreas Schwab
2007-02-26 10:02 ` Richard Purdie [this message]
2007-02-26 10:02 ` Richard Purdie
2007-02-26 21:54 ` Andreas Schwab
2007-02-26 21:54 ` Andreas Schwab
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=1172484121.5824.1.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@suse.de \
/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.