public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Julien BLACHE <jb@jblache.org>
Cc: Soeren Sonnenburg <sonne@debian.org>,
	nicolas@boichat.ch, felipe_alfaro@linuxmail.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Brightness control for MacBook Pro - Nvidia 9400
Date: Fri, 12 Feb 2010 14:14:57 +0000	[thread overview]
Message-ID: <20100212141457.GA18714@srcf.ucam.org> (raw)
In-Reply-To: <878wayk8hn.fsf@sonic.technologeek.org>

On Fri, Feb 12, 2010 at 12:18:28PM +0100, Julien BLACHE wrote:
> Soeren Sonnenburg <sonne@debian.org> wrote:
> 
> Hi,
> 
> > I am booting a MacBookPro5,3 using elilo and efifb. Now I'd like to use
> > pommed to control display brightness (which won't work). Digging around
> > in mbp_nvidia_bl.c I figured out that tries to control the geforce 9600M
> > instead of the currently active geforece 9400m
> 
> If you know how one can determine which GPU is active, let me know. I
> don't have this information at the moment.

There's a _DSM method in the ACPI tables that you need to execute.

> I'm not sure this method actually works without the legacy BIOS. IIRC
> that method was determined by reverse engineering the Windows drivers,
> which means the legacy BIOS was in use.

Ah, yes - sorry, I'd forgotten that this used the smi horror. nouveau 
should drive the chip brightness natively, so it's probably better to 
figure out why it's breaking rather than worry about this...

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-02-12 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 20:38 Brightness control for MacBook Pro - Nvidia 9400 Soeren Sonnenburg
2010-02-11 20:44 ` Matthew Garrett
2010-02-11 23:13   ` Soeren Sonnenburg
2010-02-12 11:18 ` Julien BLACHE
2010-02-12 14:14   ` Matthew Garrett [this message]
2010-02-12 16:25     ` Julien BLACHE
2010-02-12 16:28       ` Matthew Garrett
2010-02-12 16:42         ` Soeren Sonnenburg
2010-02-12 16:44           ` Matthew Garrett
2010-02-12 16:55             ` Soeren Sonnenburg

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=20100212141457.GA18714@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=jb@jblache.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas@boichat.ch \
    --cc=sonne@debian.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