public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
	Terence Ripperda <tripperda@nvidia.com>,
	"lenb@kernel.org" <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: patch for video.c driver
Date: Fri, 13 Mar 2009 18:11:18 +0100	[thread overview]
Message-ID: <200903131811.19209.rjw@sisk.pl> (raw)
In-Reply-To: <20090313030030.GA23571@srcf.ucam.org>

On Friday 13 March 2009, Matthew Garrett wrote:
> On Fri, Mar 13, 2009 at 10:08:12AM +0800, Zhang Rui wrote:
> > On Thu, 2009-03-12 at 23:47 +0800, Terence Ripperda wrote:
> > >  The intent was to follow the same architecture that the
> > > video.ko driver already follows and to make the support generic enough for
> > > many different users. For example, above I mentioned that both NVIDIA and
> > > other vendors have ACPI extension methods, the support we're adding would be
> > > usable by all such vendors.
> > 
> > Makes sense, although the other vendors usually offers a platform
> > specific device rather than a platform specific control method.
> 
> Mm. I don't see any reason for video output switching to be handled in 
> kernel. It's fundamentally behaviour that depends on the user's 
> preferences, so the logical way to handle this is for the event to be 
> sent to userland (as it is currently) and for a userspace agent to then 
> turn this into an xrandr event. The only thing that currently prevents 
> this from working with the binary nvidia drivers is the fact that they 
> don't appear to support xrandr for output control. I'd prefer it if we 
> didn't work around X driver shortcomings by adding interfaces to the 
> kernel.

FWIW, agreed.

Thanks,
Rafael

  reply	other threads:[~2009-03-13 17:11 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 [this message]
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

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=200903131811.19209.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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