From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83226] Allow use of ColorRange and ColorSpace in xorg.conf.d files
Date: Tue, 24 Feb 2015 14:36:29 +0000 [thread overview]
Message-ID: <bug-83226-502-31oxGM52ex@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83226-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83226
--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Andy Furniss from comment #13)
>
> I added a couple of DRM_ERROR... lines to see if I passed
> if(drm_rgb_quant_range_selectable and I don't.
>
> But even if I did I don't think that patch will work as I only get one
> message at the start - I would have expected that flipping between tvrgb and
> bypass (which works OK) would have generated more, but it doesn't.
Changing the AVI infoframe requires a full modeset, changing the output_csc
does not. The AVI infoframe change only takes affect when you force a full
modeset (e.g., switch modes with xrandr). It's trivial to change the code to
force a full modeset rather than just updating the output_csc state when you
update the property, but I left them decoupled now for testing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-24 14:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 7:27 [Bug 83226] New: Allow use of ColorRange and ColorSpace in xorg.conf.d files bugzilla-daemon
2015-02-21 22:54 ` [Bug 83226] " bugzilla-daemon
2015-02-22 7:10 ` bugzilla-daemon
2015-02-23 16:17 ` bugzilla-daemon
2015-02-23 16:17 ` bugzilla-daemon
2015-02-23 20:53 ` bugzilla-daemon
2015-02-23 20:56 ` bugzilla-daemon
2015-02-23 21:45 ` bugzilla-daemon
2015-02-23 22:19 ` bugzilla-daemon
2015-02-24 0:12 ` bugzilla-daemon
2015-02-24 2:32 ` bugzilla-daemon
2015-02-24 7:26 ` bugzilla-daemon
2015-02-24 10:15 ` bugzilla-daemon
2015-02-24 11:40 ` bugzilla-daemon
2015-02-24 12:23 ` bugzilla-daemon
2015-02-24 14:36 ` bugzilla-daemon [this message]
2015-02-24 22:38 ` bugzilla-daemon
2015-02-25 10:00 ` bugzilla-daemon
2015-02-25 15:04 ` bugzilla-daemon
2015-02-26 15:03 ` bugzilla-daemon
2015-02-26 15:25 ` bugzilla-daemon
2015-02-26 15:31 ` bugzilla-daemon
2015-03-27 13:08 ` bugzilla-daemon
2015-03-27 13:29 ` bugzilla-daemon
2015-05-02 3:04 ` bugzilla-daemon
2015-08-19 7:07 ` bugzilla-daemon
2015-08-19 13:32 ` bugzilla-daemon
2015-08-19 13:41 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 20:43 ` bugzilla-daemon
2015-08-27 11:22 ` bugzilla-daemon
2015-08-27 13:55 ` bugzilla-daemon
2015-09-03 13:32 ` bugzilla-daemon
2016-06-05 14:04 ` bugzilla-daemon
2019-09-25 17:51 ` bugzilla-daemon
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=bug-83226-502-31oxGM52ex@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).