Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Florian Mickler
On Sun, 05 Dec 2010 13:08:18 -0800 Keith Packard wrote: > On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler > wrote: > > On Fri, 26 Nov 2010 10:45:59 -0800 > > Keith Packard wrote: > > > > > In order to correctly report monitor connected status changes, the > > > previous monitor status must

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Florian Mickler
On Sun, 05 Dec 2010 13:08:18 -0800 Keith Packard wrote: > On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler > wrote: > > On Fri, 26 Nov 2010 10:45:59 -0800 > > Keith Packard wrote: > > > > > In order to correctly report monitor connected status changes, the > > > previous monitor status must

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Chris Wilson
On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler 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. -Chris -- Chris Wilson, Intel Open So

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Keith Packard
On Wed, 08 Dec 2010 17:08:04 +, Chris Wilson wrote: > On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler > 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 o

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Keith Packard
On Wed, 08 Dec 2010 17:08:04 +, Chris Wilson wrote: > On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler > 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 o

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-08 Thread Chris Wilson
On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler 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. -Chris -- Chris Wilson, Intel Open Sou

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Florian Mickler
On Fri, 26 Nov 2010 10:45:59 -0800 Keith Packard wrote: > In order to correctly report monitor connected status changes, the > previous monitor status must be recorded in the connector->status > value instead of being discarded. > > Signed-off-by: Keith Packard Keith, am I right to assume that

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Florian Mickler
On Fri, 26 Nov 2010 10:45:59 -0800 Keith Packard wrote: > In order to correctly report monitor connected status changes, the > previous monitor status must be recorded in the connector->status > value instead of being discarded. > > Signed-off-by: Keith Packard Keith, am I right to assume that

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Keith Packard
On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler wrote: > On Fri, 26 Nov 2010 10:45:59 -0800 > Keith Packard wrote: > > > In order to correctly report monitor connected status changes, the > > previous monitor status must be recorded in the connector->status > > value instead of being discarde

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Keith Packard
On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler wrote: > On Fri, 26 Nov 2010 10:45:59 -0800 > Keith Packard wrote: > > > In order to correctly report monitor connected status changes, the > > previous monitor status must be recorded in the connector->status > > value instead of being discard

[PATCH 2/2] drm: record monitor status in output_poll_execute

2010-11-26 Thread Keith Packard
In order to correctly report monitor connected status changes, the previous monitor status must be recorded in the connector->status value instead of being discarded. Signed-off-by: Keith Packard --- drivers/gpu/drm/drm_crtc_helper.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(

[PATCH 2/2] drm: record monitor status in output_poll_execute

2010-11-26 Thread Keith Packard
In order to correctly report monitor connected status changes, the previous monitor status must be recorded in the connector->status value instead of being discarded. Signed-off-by: Keith Packard --- drivers/gpu/drm/drm_crtc_helper.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(