public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: Zhang Rui <rui.zhang@intel.com>, linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: patch for video.c driver
Date: Sat, 14 Mar 2009 03:55:06 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0903140314200.23716@localhost.localdomain> (raw)
In-Reply-To: <1236910092.2807.103.camel@rzhang-dt>

Terence,

First, I'm delighted to hear from nvidia -- thanks
for reaching out to the Linux community.

a couple of observations...

drivers/acpi/*.c in general, and video.c in particular,
are meant to implement what is documented in the ACPI specification.

Linux has moved the vendor specific drivers (that may use ACPI,
or use vendor-specific ACPI extensions)
to drivers/platform/x86/*.c

That is where I'd generally expect an nvidia-specific ACPI extension to 
live.

Is there any public documentationon how NVIF is supposed to operate?

I have a new snappy Sony laptop that has both nvidia and intel graphics,
and it has an NVIF.  I'm certain that Linux has no idea how to
switch between "Stamina" and "Speed" modes...

But I also have a Lenovo T61 with only Intel graphics,
and it still has an NVIF.  (presumably Lenovo ships one
BIOS for both their Intel and Nvidia based T61's...)
What happens with NVIF in this case?

thanks,
-Len


      parent reply	other threads:[~2009-03-14  7:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090312154741.GA1055@hygelac>
2009-03-13  2:08 ` patch for video.c driver Zhang Rui
2009-03-13  3:00   ` Matthew Garrett
2009-03-13 17:11     ` Rafael J. Wysocki
2009-03-13 17:36     ` Terence Ripperda
2009-03-13 17:47       ` Matthew Garrett
2009-03-13 17:58         ` Terence Ripperda
2009-03-13 18:06           ` Matthew Garrett
2009-03-13 20:45             ` Terence Ripperda
2009-03-13 20:52               ` Matthew Garrett
2009-03-14  7:55   ` Len Brown [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=alpine.LFD.2.00.0903140314200.23716@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=tripperda@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox