From: Thomas Renninger <trenn@suse.de>
To: linux-acpi <linux-acpi@vger.kernel.org>
Cc: ibm-acpi-devel <ibm-acpi-devel@lists.sourceforge.net>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] Untested proposal patch: Store video capabilities of BIOS globally at ACPI parse time and export it.
Date: Wed, 17 Oct 2007 16:35:29 +0200 [thread overview]
Message-ID: <1192631729.9847.678.camel@queen.suse.de> (raw)
In-Reply-To: <1192466754.9847.594.camel@queen.suse.de>
On Mon, 2007-10-15 at 18:45 +0200, Thomas Renninger wrote:
> Store video capabilities of BIOS globally at ACPI parse time and export it.
>
> This is for vendor specific vs video driver so that they can distinguish who
> should take care of video/brightness control.
> The bits are chosen in a way that video can handle the ability gracefully
> if all the checked functions are there...
>
> Vendor specific modules must check on that bits and take their hands off
> brightness/video control when set, as they are then served by the video
> driver.
>
> This hasn't been tested yet. It's more a proposal whether this is the way
> to go...
> Would be great if someone could give it a test if accepted, I will test
> this also as soon as some positive feedback is popping up.
>
> + success:
> + acpi_walk_namespace(ACPI_TYPE_METHOD, device->handle, ACPI_UINT32_MAX,
> + acpi_brighntess_cap_match, NULL, NULL);
This has been tested now and and it works fine if ACPI_TYPE_METHOD is
replaced with ACPI_TYPE_DEVICE.
Oh, Len was not in CC on the original post..:
Please tell me if you like to take it and if, whether you replace this
METHOD <-> DEVICE manually or if you like to have it reposted.
Thanks,
Thomas
prev parent reply other threads:[~2007-10-17 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:45 [PATCH] Untested proposal patch: Store video capabilities of BIOS globally at ACPI parse time and export it Thomas Renninger
[not found] ` <1192466754.9847.594.camel-X8wR35IVlAxolqkO4TVVkw@public.gmane.org>
2007-10-15 16:52 ` Matthew Garrett
2007-10-17 14:35 ` Thomas Renninger [this message]
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=1192631729.9847.678.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--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