All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Frank Murphy <murphyf+xfree86@f-m.fm>
Cc: debian-x@lists.debian.org, linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: G3 iBook LCD brightness in X under kernel 2.4.25 and 2.6.8
Date: Mon, 29 Nov 2004 07:39:39 +1100	[thread overview]
Message-ID: <1101674379.4653.9.camel@gaston> (raw)
In-Reply-To: <200411282114.48141.murphyf+xfree86@f-m.fm>

On Sun, 2004-11-28 at 21:14 +0100, Frank Murphy wrote:
> On Sunday 28 November 2004 2:58, Benjamin Herrenschmidt wrote:
> > >
> > > So I've tried this using the stock Debian 2.6.8 and 2.6.9 PPC kernels
> > > with the same results.
> > >
> > > $ grep ATY /boot/config-2.6.9-powerpc
> > > CONFIG_FB_ATY128=y
> > > CONFIG_FB_ATY=y
> > > CONFIG_FB_ATY_CT=y
> > > CONFIG_FB_ATY_GX=y
> > > # CONFIG_FB_ATY_XL_INIT is not set
> > >
> > > It seems that the atyfb module is compiled in. Is there another way to
> > > check?
> >
> > Check the bits in CONFIG_PMAC_BACKLIGHT in atyfb (like, add some
> > printk's to see if they are reached etc..)
> 
> So I added a couple of printk()s like you asked. I added one to 
> aty128fb_blank() in aty128fb.c:2037 and two to aty_init() in 
> atyfb_base.c:1793 and 1802 (inside the 'if (M64_HAS(MOBIL_BUS))'). The one I 
> added to aty128fb didn't print (as expected), but both of them from 
> atyfb_base.c printed. So it seems that CONFIG_PMAC_BACKLIGHT is properly 
> defined. Anything you'd specifically like me to try?

Well, the backlight control is done by writing to one of the LCD
register, you can try to track down the values in there and eventually
compare with 2.4

> I find it interesting that in the console the dimming works. I thought that on 
> PPC the console used the framebuffer. Another notable thing is that while in 
> X, the dimming doesn't work, but when I switch to one of the VTs, the screen 
> brightness is adjusted to what it should have been in X.

Ah ? What do you mean by "dimming" ? blanking ? or backlight control ?

Could be some crap done by the X driver ... It's notoriously allergic to
fbdev's ... I'll have to double check.

> Thanks for your help on this,
> 
> Frank
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>

  reply	other threads:[~2004-11-28 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200411232008.16854.murphyf+xfree86@f-m.fm>
2004-11-26 10:28 ` G3 iBook LCD brightness in X under kernel 2.4.25 and 2.6.8 Christof Petig
2004-11-26 15:38   ` murphyf+xfree86
2004-11-27  1:02   ` Benjamin Herrenschmidt
2004-11-27  8:48     ` Frank Murphy
2004-11-28  1:58       ` Benjamin Herrenschmidt
2004-11-28 20:14         ` Frank Murphy
2004-11-28 20:39           ` Benjamin Herrenschmidt [this message]
2004-11-29  9:42             ` Frank Murphy
2004-11-29 17:17               ` Christof Petig
2004-11-30  8:02                 ` Christof Petig
2004-11-30  9:05                   ` Frank Murphy
2004-12-01  8:25                     ` murphyf+xfree86
2004-11-29 21:56               ` Benjamin Herrenschmidt
2004-11-29  0:45     ` Christof Petig

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=1101674379.4653.9.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=debian-x@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=murphyf+xfree86@f-m.fm \
    /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.