From: Dave Airlie <airlied@redhat.com>
To: Julien Cristau <jcristau@debian.org>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>,
intel-gfx@lists.freedesktop.org, stable@kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm: Hold the mode mutex whilst probing for sysfs status
Date: Wed, 16 Mar 2011 09:00:33 +1000 [thread overview]
Message-ID: <1300230033.31546.11.camel@clockmaker-el6> (raw)
In-Reply-To: <20110315123158.GP2933@radis.liafa.jussieu.fr>
On Tue, 2011-03-15 at 13:31 +0100, Julien Cristau wrote:
> On Tue, Mar 15, 2011 at 11:40:00 +0000, Chris Wilson wrote:
>
> > [Digression: what is upowerd doing reading those power hungry files?]
> >
> Apparently, checking "docked" status every 30 seconds, by reading the
> status of drm outputs. Where "docked" means "more than one output
> connected". Yes, it's silly.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613745
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618329
>
Its also now disabled by default upstream.
I think he was using an 965 or GM45 laptop that seemed to not report
output changes properly.
Dave.
next prev parent reply other threads:[~2011-03-15 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 9:35 Linux 2.6.37-2, 2.14.0-4: BUG: unable to handle kernel NULL pointer dereference at 00000100; IP: [<e0c22019>] intel_tv_detect_type+0xa2/0x203 [i915] Paul Menzel
2011-03-15 11:40 ` [PATCH] drm: Hold the mode mutex whilst probing for sysfs status Chris Wilson
2011-03-15 12:31 ` [Intel-gfx] " Julien Cristau
2011-03-15 23:00 ` Dave Airlie [this message]
2011-03-15 15:35 ` Jesse Barnes
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=1300230033.31546.11.camel@clockmaker-el6 \
--to=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jcristau@debian.org \
--cc=paulepanter@users.sourceforge.net \
--cc=stable@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.