All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:33:20 +0000	[thread overview]
Message-ID: <20090316113320.GA18455@srcf.ucam.org> (raw)
In-Reply-To: <20090316112851.GB28025@kamineko.org>

On Mon, Mar 16, 2009 at 08:28:51PM +0900, Mattia Dongili wrote:
> On Mon, Mar 16, 2009 at 10:24:23AM +0000, Matthew Garrett wrote:
> > _DSM is "Device Specific Method". The magic numbers it requires are 
> > interface descriptions. How many of these machines have nvidia-based 
> > dual GPU architectures?
> 
> SZ and Z have dual GPUs (Intel onboard + NVidia), TT doesn't.

There's been two generations of dual GPU machines - ones that support 
runtime switching (whih I think is limited to the Z?) and ones that 
don't (the early SZs at least, probably all of them). The _DSM stuff 
we're interested in is for the runtime switching.

> >                         Are the _DSM methods always attached to the 
> > nvidia device?
> 
> As far as I can see the Z is the only one having it attached to the
> nvidia device.

In that case I think we're fine only worrying about that case. The 
interesting thing now is in whether this is Sony-specific or whether the 
same method is specified for other systems switching between the nvidia 
chipsets.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2009-03-16 11:33 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
2009-03-16 11:28         ` Mattia Dongili
2009-03-16 11:33           ` Matthew Garrett [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=20090316113320.GA18455@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.