From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: "Zhang, Rui" <rui.zhang@intel.com>, lenb <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
linux-gfx@linux.intel.com
Subject: Re: [PATCH 2/4] ACPI: video: prevent ACPI video actions upondisplay switch notifications
Date: Wed, 12 Mar 2008 18:09:58 +0000 [thread overview]
Message-ID: <20080312180958.GA29487@srcf.ucam.org> (raw)
In-Reply-To: <1205338005.29877.247.camel@queen.suse.de>
On Wed, Mar 12, 2008 at 05:06:45PM +0100, 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.
Setting my HP 2510p to a DOS of 0 leaves it smashing CPU state on every
other lid open event, so I suspect it's not tested at all. I'd lean
towards saying that the kernel default should probably be 1, with
userspace altering that as appropriate.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-03-12 18:10 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
2008-03-14 2:12 ` Zhang, Rui
2008-03-12 18:09 ` Matthew Garrett [this message]
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=20080312180958.GA29487@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.