From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Florian Mickler <florian@mickler.org>
Cc: Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute
Date: Wed, 08 Dec 2010 09:30:00 -0800 [thread overview]
Message-ID: <yun1v5sb2av.fsf@aiko.keithp.com> (raw)
In-Reply-To: <0d30dc$kddq6q@orsmga001.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Wed, 08 Dec 2010 17:08:04 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler <florian@mickler.org> wrote:
> > Does that mean that the kernel regression will not be
> > fixed/worked-around for old userspace?
>
> I think there is some confusion in that I believe there is more than one
> backlight bug at play here.
The kernel and user space fixes addressed the same technical problem
(failing to note that mode setting turned on the devices), but the
symptoms that this caused were different; in kernel mode, the result
would be that monitors would be left turned on when user space asked
that they be turned off (and left pointing at random memory too, which
was amusing). I think that the backlight issue was caused by the
user-space bug though.
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2010-12-08 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 18:45 [PATCH 1/2] drm: Set connector DPMS status to ON in drm_crtc_helper_set_config Keith Packard
2010-11-26 18:45 ` Keith Packard
2010-11-26 18:45 ` [PATCH 2/2] drm: record monitor status in output_poll_execute Keith Packard
2010-12-05 12:27 ` [Intel-gfx] " Florian Mickler
2010-12-05 21:08 ` Keith Packard
2010-12-08 16:34 ` Florian Mickler
2010-12-08 17:08 ` Chris Wilson
2010-12-08 17:30 ` Keith Packard [this message]
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=yun1v5sb2av.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian@mickler.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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.