[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200611061742.27298.len.brown@intel.com>
Date: Mon, 6 Nov 2006 17:42:26 -0500
From: Len Brown <len.brown@...el.com>
To: Greg KH <greg@...ah.com>
Cc: Yu Luming <luming.yu@...il.com>, Andrew Morton <akpm@...l.org>,
Pavel Machek <pavel@....cz>,
Matt Domsch <Matt_Domsch@...l.com>,
Alessandro Guido <alessandro.guido@...il.com>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
jengelh@...ux01.gwdg.de, gelma@...ma.net, ismail@...dus.org.tr,
Richard Hughes <hughsient@...il.com>
Subject: Re: [patch 4/6] Add output class document
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists