From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Albert Vilella <avilella@gmail.com>
Cc: Matthias Welwarsky <matze@welwarsky.de>, linux-acpi@vger.kernel.org
Subject: Re: new fixes for sony-acpi
Date: Sat, 28 Mar 2009 12:19:54 +0000 [thread overview]
Message-ID: <20090328121954.GA24289@srcf.ucam.org> (raw)
In-Reply-To: <358f4d650903280511r1c7ba88an14226c2f8f1438d8@mail.gmail.com>
On Sat, Mar 28, 2009 at 12:11:51PM +0000, Albert Vilella wrote:
> I am right in thinking that reading the DSDT tables for hybrid
> graphics laptops is sufficient to infer their workings?
Yes, though nvidia and AMD use quite different approaches to this. The
nvidia chips all appear to have a _DSM with the same UUID.
> I've been compiling a list of hybrid graphics laptops and been asking
> people to provide their DSDT tables
> in this bug report:
> https://bugs.launchpad.net/bugs/312756
Ah, convenient, thanks! I'd only had the Thinkpad DSDT to look at so
far, so this gives me a chance to work out if there's any
standardisation of the AMD approach.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-03-28 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 16:34 new fixes for sony-acpi Norbert Preining
2009-03-28 1:34 ` Len Brown
2009-03-28 1:38 ` Matthew Garrett
2009-03-28 8:33 ` Norbert Preining
2009-03-28 12:00 ` Matthew Garrett
2009-03-31 15:20 ` Matthew Garrett
2009-04-13 15:03 ` Norbert Preining
2009-04-13 15:06 ` Matthew Garrett
2009-04-13 15:11 ` Norbert Preining
2009-04-13 15:26 ` Matthew Garrett
2009-04-13 15:43 ` Norbert Preining
2009-04-13 15:45 ` Matthew Garrett
2009-03-28 8:41 ` Matthias Welwarsky
2009-03-28 12:11 ` Albert Vilella
2009-03-28 12:19 ` Matthew Garrett [this message]
2009-03-28 12:22 ` Matthew Garrett
2009-03-28 14:19 ` Matthias Welwarsky
2009-03-28 14:44 ` Matthew Garrett
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=20090328121954.GA24289@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=avilella@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=matze@welwarsky.de \
/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