From: Daniel Vetter <daniel@ffwll.ch>
To: Mario Kleiner <mario.kleiner.de@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Legacy gamma table updates broken in 4.7-rc4
Date: Tue, 12 Jul 2016 15:49:24 +0200 [thread overview]
Message-ID: <20160712134924.GD23520@phenom.ffwll.local> (raw)
In-Reply-To: <577CDCE4.1090502@gmail.com>
On Wed, Jul 06, 2016 at 12:26:44PM +0200, Mario Kleiner wrote:
> A strange one. In Linux 4.7-rc4, at least as build by the Ubuntu mainline
> ppa, gamma table updates via RandR don't work. No errors are reported and
> the X-Server thinks everything went well, but on Intel Ironlake and
> Ivybridge the updates don't have any visual effect.
>
> The same problem doesn't happen with current drm-next, so something was
> fixed. Looking at the new code in intel_color.c i can't see anything obvious
> that would break it on 4.7-rc but make it work on drm-next?
>
> Are there some gamma fixes in drm-next that didn't make it into 4.7-rc yet?
Not sure what's going on, but might need a reverse bisect to cherry-pick
the fixes over. It's indeed supposed to keep working. Lionel has been
working on this, adding him.
-Daniel
>
> Thanks,
> -mario
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-07-12 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:26 Legacy gamma table updates broken in 4.7-rc4 Mario Kleiner
2016-07-12 13:49 ` Daniel Vetter [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=20160712134924.GD23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mario.kleiner.de@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox