All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] intel: Listen for hotplug uevents (V2)
Date: Mon, 04 Oct 2010 10:25:35 +0100	[thread overview]
Message-ID: <89kc63$i8kj1h@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1286147296-12531-1-git-send-email-keithp@keithp.com>

On Sun,  3 Oct 2010 16:08:16 -0700, Keith Packard <keithp@keithp.com> wrote:
> From: Adam Jackson <ajax@redhat.com>
> 
> This connects the kernel uevent indicating monitor hotplugging to the
> RandR notification events so that X applications can be notified
> automatically when monitors are connected or disconnected.

The obvious question: why are we doing this in the driver? It looks very
generic and can be shared between any of the drm drivers, so should this
be a facility provided by the server? It would be a good start to a KMS
module...
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  parent reply	other threads:[~2010-10-04  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 22:13 [PATCH] intel: Listen for hotplug uevents Keith Packard
2010-10-03 23:08 ` [PATCH] intel: Listen for hotplug uevents (V2) Keith Packard
2010-10-03 23:15   ` Peter Stuge
2010-10-03 23:34     ` Keith Packard
2010-10-04  9:25   ` Chris Wilson [this message]
2010-10-04 10:51   ` Geir Ove Myhr
2010-10-04 17:43     ` [PATCH] intel: Listen for hotplug uevents (V3) Keith Packard
2010-10-04 20:57       ` Geir Ove Myhr

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='89kc63$i8kj1h@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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.