From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mattia Dongili <malattia@linux.it>
Cc: Zhang Rui <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: The Garbled screen issue on Sony laptops with two graphics (Intel and Nvidia)
Date: Mon, 16 Mar 2009 10:24:23 +0000 [thread overview]
Message-ID: <20090316102423.GA16889@srcf.ucam.org> (raw)
In-Reply-To: <20090311130847.GC13101@kamineko.org>
On Wed, Mar 11, 2009 at 10:08:47PM +0900, Mattia Dongili wrote:
> - some models have different magic numbers for the _DSM invocation, from
> the DSDT I have available:
> DSDT.sz.xxx.dsl (some uknown model)
> DSDT.sz61mn-forXP.dsl
> DSDT.tt11lnb.dsl
> DSDT.z11vn.dsl
> DSDT.z90s.dsl
> VGN-SZ4XWNC-R0111N0.dsl
> and for what I can see, z and tt have the same magic numbers while the
> sz has different ones. So the code that calls _DSM will need to have
> some DMI switch to make sure we are calling it with the right
> parameters (for now supporting z and tt might be enough)
_DSM is "Device Specific Method". The magic numbers it requires are
interface descriptions. How many of these machines have nvidia-based
dual GPU architectures? Are the _DSM methods always attached to the
nvidia device?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-03-16 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 2:45 The Garbled screen issue on Sony laptops with two graphics (Intel and Nvidia) Zhang Rui
2009-03-11 2:46 ` Matthew Garrett
2009-03-11 7:29 ` Zhang Rui
2009-03-11 7:30 ` Zhang Rui
2009-03-11 12:47 ` Matthew Garrett
2009-03-11 13:08 ` Mattia Dongili
2009-03-16 5:46 ` Zhang Rui
2009-03-16 10:24 ` Matthew Garrett [this message]
2009-03-16 11:28 ` Mattia Dongili
2009-03-16 11:33 ` 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=20090316102423.GA16889@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
--cc=rui.zhang@intel.com \
--cc=zhenyu.z.wang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.