[Intel-gfx] [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-04 Thread Geir Ove Myhr
On Mon, Oct 4, 2010 at 1:08 AM, Keith Packard wrote: > From: Adam Jackson > ... > +++ b/src/intel_driver.c > @@ -107,6 +107,7 @@ typedef enum { > ? ?OPTION_DEBUG_FLUSH_BATCHES, > ? ?OPTION_DEBUG_FLUSH_CACHES, > ? ?OPTION_DEBUG_WAIT, > + ? OPTION_HOTPLUG, > ?} I830Opts; > > ?static OptionInfoRec I

[Intel-gfx] [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-04 Thread Chris Wilson
On Sun, 3 Oct 2010 16:08:16 -0700, Keith Packard wrote: > From: Adam Jackson > > 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 que

Re: [Intel-gfx] [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-04 Thread Chris Wilson
On Sun, 3 Oct 2010 16:08:16 -0700, Keith Packard wrote: > From: Adam Jackson > > 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 que

Re: [Intel-gfx] [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-04 Thread Geir Ove Myhr
On Mon, Oct 4, 2010 at 1:08 AM, Keith Packard wrote: > From: Adam Jackson > ... > +++ b/src/intel_driver.c > @@ -107,6 +107,7 @@ typedef enum { >    OPTION_DEBUG_FLUSH_BATCHES, >    OPTION_DEBUG_FLUSH_CACHES, >    OPTION_DEBUG_WAIT, > +   OPTION_HOTPLUG, >  } I830Opts; > >  static OptionInfoRec I

[PATCH] intel: Listen for hotplug uevents (V2)

2010-10-04 Thread Peter Stuge
Keith Packard wrote: > 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. Are these events actually being generated? If there is the infrastructure to

Re: [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-03 Thread Keith Packard
On Mon, 4 Oct 2010 01:15:08 +0200, Peter Stuge wrote: > If there is the infrastructure to do so, then it seems that the 600ms > delay while polling unconnected monitors could easily be removed. Newer hardware generates interrupts for VGA and TV hotplug events; older hardware doesn't. -- keith.

[PATCH] intel: Listen for hotplug uevents (V2)

2010-10-03 Thread Keith Packard
On Mon, 4 Oct 2010 01:15:08 +0200, Peter Stuge wrote: > If there is the infrastructure to do so, then it seems that the 600ms > delay while polling unconnected monitors could easily be removed. Newer hardware generates interrupts for VGA and TV hotplug events; older hardware doesn't. -- keith.

Re: [PATCH] intel: Listen for hotplug uevents (V2)

2010-10-03 Thread Peter Stuge
Keith Packard wrote: > 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. Are these events actually being generated? If there is the infrastructure to

[PATCH] intel: Listen for hotplug uevents (V2)

2010-10-03 Thread Keith Packard
From: Adam Jackson 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. This also adds a configuration option to disable hotplug events. V2: missed a #ifd

[PATCH] intel: Listen for hotplug uevents (V2)

2010-10-03 Thread Keith Packard
From: Adam Jackson 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. This also adds a configuration option to disable hotplug events. V2: missed a #ifd