From: Len Brown <len.brown@intel.com>
To: Greg KH <greg@kroah.com>
Cc: Yu Luming <luming.yu@gmail.com>, Andrew Morton <akpm@osdl.org>,
Pavel Machek <pavel@ucw.cz>, Matt Domsch <Matt_Domsch@dell.com>,
Alessandro Guido <alessandro.guido@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
jengelh@linux01.gwdg.de, gelma@gelma.net, ismail@pardus.org.tr,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [patch 4/6] Add output class document
Date: Mon, 6 Nov 2006 17:42:26 -0500 [thread overview]
Message-ID: <200611061742.27298.len.brown@intel.com> (raw)
In-Reply-To: <20061104082228.GA30489@kroah.com>
On Saturday 04 November 2006 03:22, Greg KH wrote:
> On Sat, Nov 04, 2006 at 09:22:00PM +0800, Yu Luming wrote:
> Have you been working with the X developers that have been doing a lot
> of work in describing and interacting with these different video
> devices? I think you might want to work with them so that you don't
> create an interface that will not be used by them.
We discussed this with Keith Packard, who insisted that video switching
is best done from within the video driver using native hardware interfaces.
That sounds good to me, but it doesn't answer the question about
systems who choose to export video switching via ACPI.
The goal at hand is to export that capability in the event
it is not available via other means.
The issue that will come up is if this capability and a native
hardware technique are used at the same time -- probably
bad things will happen. In that case, we need a way for
the native technique to disable use of the ACPI technique.
cheers,
-Len
next prev parent reply other threads:[~2006-11-06 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 13:22 [patch 4/6] Add output class document Yu Luming
2006-11-02 14:04 ` Timo Hoenig
2006-11-04 8:22 ` Greg KH
2006-11-06 22:42 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 13:23 Yu Luming
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=200611061742.27298.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alessandro.guido@gmail.com \
--cc=gelma@gelma.net \
--cc=greg@kroah.com \
--cc=hughsient@gmail.com \
--cc=ismail@pardus.org.tr \
--cc=jengelh@linux01.gwdg.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=pavel@ucw.cz \
/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