public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: linux-acpi@vger.kernel.org
Subject: video patches in ACPI test tree
Date: Sat, 08 Nov 2008 01:14:19 -0500	[thread overview]
Message-ID: <1226124869-1878-1-git-send-email-lenb@kernel.org> (raw)

Here are the video patches as refreshed in the ACPI test branch.
(there are a couple of merge conflicts, since there are other
 patches in the acpi test tree that touch the same files)

I've tested my T61 (Intel Graphics, and thus IGD support)
and found that these patches do no harm.

in all cases, I load i915, video and thinkpad_acpi

2.6.27:
Brightness hotkeys display controls in X,
but have no actual effect on brightness
/sys/class/backlight/acpi_video0 has no effect
/sys/class/backlight/acpi_video1 works

2.6.28-rc3+:
Brightness hotkeys display controls in X,
and correctly control brightness
/sys/class/backlight/acpi_video0 works
/sys/class/backlight/acpi_video1 works

2.6.28-rc3+ with these patches:
same as 2.6.28-rc3+, except
/sys/class/backlight/acpi_video1 does not exist.

thanks,
-Len



             reply	other threads:[~2008-11-08  6:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  6:14 Len Brown [this message]
2008-11-08  6:14 ` [PATCH 01/10] ACPI: video: Ignore devices that aren't present in hardware Len Brown
2008-11-08  6:14 ` [PATCH 02/10] ACPI video: if no ACPI backlight support, use vendor drivers Len Brown
2008-11-08  6:14 ` [PATCH 03/10] Acer-WMI: fingers off backlight if video.ko is serving this functionality Len Brown
2008-11-08  6:14 ` [PATCH 04/10] asus-acpi: " Len Brown
2008-11-08  6:14 ` [PATCH 05/10] compal: " Len Brown
2008-11-08  6:14 ` [PATCH 06/10] eeepc-laptop: " Len Brown
2008-11-08  6:14 ` [PATCH 07/10] fujitsu-laptop: " Len Brown
2008-11-08  6:14 ` [PATCH 08/10] msi-laptop: " Len Brown
2008-11-08  6:14 ` [PATCH 09/10] sony-laptop: " Len Brown
2008-11-08  6:14 ` [PATCH 10/10] thinkpad_acpi: " Len Brown

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=1226124869-1878-1-git-send-email-lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.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