public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: linux-gfx@linux.intel.com, trenn@suse.de
Cc: "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 10:35:40 -0700	[thread overview]
Message-ID: <200803121035.40860.jesse.barnes@intel.com> (raw)
In-Reply-To: <1205338005.29877.247.camel@queen.suse.de>

On Wednesday, March 12, 2008 9:06 am Thomas Renninger wrote:
> Above was not from myself, but copied out from the bug.
> The guy(s) complained that DOS=0 now breaks their machines...
> I try to find some time to look at this a bit deeper and will then
> comment in the bug (can take some time...).
> IMO recent HPs can/should be taken as a reference as they tend to stick
> to the ACPI spec closely.
> As said, it was late and I mixed up patches, the patch to switch _DOS
> default value to 0 was already in 2.6.24?
> I don't know now how much was tried already.
> A) To switch DOS to 0 when e.g. intel graphics driver gets active
> (should be done by the graphics driver package or if X is started if the
> driver is aware of the hotkey and can do the switching).
> B) Otherwise (e.g. if framebuffer or graphics driver which do not switch
> the display) it should stay to be BIOS handled.
> This is the correct way IMO this should get handled.
>
> Puhh, this needs a lot testing (different graphics drivers, different
> machines,...) and implementation to switch to DOS=0 in graphics
> drivers...

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.

The trouble is that DOS=0 works for some machines but breaks others, does 
anyone have a summary of the reports against the various values?

Jesse

  reply	other threads:[~2008-03-12 17:36 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         ` Jesse Barnes [this message]
2008-03-12 18:01           ` [Linux-gfx] " Henrique de Moraes Holschuh
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=200803121035.40860.jesse.barnes@intel.com \
    --to=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