From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/3] X86 drivers: Introduce msi-wmi driver
Date: Mon, 26 Oct 2009 22:56:28 +0100 [thread overview]
Message-ID: <200910262256.28855.trenn@suse.de> (raw)
In-Reply-To: <20091026170421.GA3515@srcf.ucam.org>
On Monday 26 October 2009 06:04:21 pm Matthew Garrett wrote:
> Only one question - does hitting the brightness keys automatically
> change the backlight on non-ACPI backlight hardware driven by this?
Hmm, not sure what you mean with non-ACPI driven.
I can only talk about this specific model which only provides WMI (thus
also ACPI driven) backlight functionality. No generic ACPI backlight functions
as it seems only WindowsXP and not Vista is supported.
The OS has to react on WMI notifications and the brightness change only
happens when writing to IO via ACPI WSAA (WMI set block) function.
So I expect the answer to your question is no.
Thomas
BTW: Does someone know already whether Windows 7 also requires
generic ACPI backlight functions? Does someone have a good pointer to
some published Windows 7 ACPI documentation/requirements?
next prev parent reply other threads:[~2009-10-26 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:44 Introduce msi-wmi driver - Fix hp-wmi memleaks - Cleanup __cpuinit warnings Thomas Renninger
2009-10-26 16:44 ` [PATCH 1/3] X86 drivers: Introduce msi-wmi driver Thomas Renninger
2009-10-26 17:04 ` Matthew Garrett
2009-10-26 21:56 ` Thomas Renninger [this message]
2009-10-26 20:10 ` Matthew Garrett
2009-10-26 16:44 ` [PATCH 2/3] hp-wmi: Fix memleaks by freeing acpi buffers delcared as ACPI_ALLOCATE_BUFFER Thomas Renninger
2009-12-16 18:03 ` Len Brown
2009-12-16 19:20 ` Len Brown
2009-10-26 16:44 ` [PATCH 3/3] ACPI processor: Fix section mismatch for processor_add() Thomas Renninger
2009-12-16 18:15 ` 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=200910262256.28855.trenn@suse.de \
--to=trenn@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@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