From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: linux-gfx@linux.intel.com, trenn@suse.de, "Zhang,
Rui" <rui.zhang@intel.com>,
linux-acpi <linux-acpi@vger.kernel.org>, lenb <lenb@kernel.org>
Subject: Re: [Linux-gfx] Re: [PATCH 2/4] ACPI: video: prevent ACPI video actions upondisplay switch notifications
Date: Wed, 12 Mar 2008 15:01:16 -0300 [thread overview]
Message-ID: <20080312180116.GC30864@khazad-dum.debian.net> (raw)
In-Reply-To: <200803121035.40860.jesse.barnes@intel.com>
On Wed, 12 Mar 2008, Jesse Barnes wrote:
> Yeah, you're right that userspace drivers should probably set the DOS value
> when they startup, though '3' may be a better value since userspace probably
> doesn't care about the _DGS stuff.
Just punt it to userspace. Really. Never do any ACPI video display
switching actions automatically by default (unless you use a *whitelist*).
Don't set _DOS by default. Don't touch anything related to video-display
switching by default, AT ALL. Just propagate any video switching events we
get down to userspace, and that's it for default behaviour.
Add a sysfs control to let userspace ask ACPI video to handle the display
switching (as it used to). Let userspace configure how ACPI video should
behave when it gets ACPI display switch notifications.
It is one of these areas where no matter what you do, if you touch anything
you will break a box somewhere. So you just punt it to userspace, because
in userspace it is possible to have a massive DMI model database with the
proper parameters for a given userspace X.org capabilities, and a given box
AML quirks.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-03-12 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 6:47 [PATCH 2/4] ACPI: video: prevent ACPI video actions upon display switch notifications Zhang Rui
2008-02-02 3:58 ` Len Brown
2008-03-12 0:21 ` Thomas Renninger
2008-03-12 1:21 ` Thomas Renninger
2008-03-12 2:53 ` [PATCH 2/4] ACPI: video: prevent ACPI video actions upondisplay " Zhang, Rui
2008-03-12 16:06 ` Thomas Renninger
2008-03-12 17:35 ` [Linux-gfx] " Jesse Barnes
2008-03-12 18:01 ` Henrique de Moraes Holschuh [this message]
2008-03-14 2:12 ` Zhang, Rui
2008-03-12 18:09 ` Matthew Garrett
2008-03-14 2:03 ` [PATCH 2/4] ACPI: video: prevent ACPI video actionsupondisplay " Zhang, Rui
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=20080312180116.GC30864@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=jesse.barnes@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gfx@linux.intel.com \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.de \
/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