public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Add Intel ACPI IGD OpRegion support
Date: Tue, 05 Aug 2008 23:47:54 +0200	[thread overview]
Message-ID: <1217972874.4540.3.camel@hidalgo> (raw)
In-Reply-To: <1217965470.5449.4.camel@hidalgo>

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

On mar, 2008-08-05 at 21:44 +0200, Yves-Alexis Perez wrote:
> On mar, 2008-08-05 at 19:37 +0100, Matthew Garrett wrote:
> > This adds the support necessary for allowing ACPI backlight control
> > to 
> > work on some newer Intel-based graphics systems. Tested on Thinkpad
> > T61 
> > and HP 2510p hardware.
> 
> Ok, I managed to apply it against drm-2.6/drm-next but it won't apply
> against linux-acpi-2.6/test and I'm not sure how hard it is to cherry
> pick the needed stuff from drm to acpi.
> 
> I'll try to build the drm-2.6/drm-next + patch but I guess it won't be
> enough to test brightness keys?

Ok, I checked out drm-2.6/drm-next, created a local branch drm-next and
applied OpRegion.
Then I checked out linux-acpi-2.6/test, created a local branched, and
merged then my local drm-next into it.

Built fine, rebooted into single user (without using acpi_backlight=).
In single user, brightness keys still don't work.

In booted into X (with hal, powersaved, dbus etc. running), and then,
tada, brightness keys work. There is a 750ms (I guess) delay, and I
don't know who is really responsible, I guess X is. (and thus I guess
the opregion is the one needed, and X manages the brightness. If the
kernel was, it would be working even in single user)

Hope that can help understand the issues. Feel free to ask more info.

Cheers,
-- 
Yves-Alexis

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-08-05 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 18:37 [PATCH] Add Intel ACPI IGD OpRegion support Matthew Garrett
2008-08-05 19:44 ` Yves-Alexis Perez
2008-08-05 21:47   ` Yves-Alexis Perez [this message]
2008-08-06  0:13     ` Matthew Garrett
2008-08-06  2:32       ` Henrique de Moraes Holschuh
2008-08-06  5:44         ` Yves-Alexis Perez
2008-08-06  6:34         ` Matthew Garrett
2008-08-06  6:50           ` Yves-Alexis Perez
2008-08-06 12:29           ` Henrique de Moraes Holschuh

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=1217972874.4540.3.camel@hidalgo \
    --to=corsac@debian.org \
    --cc=airlied@linux.ie \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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