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: Sun, 05 Jun 2016 14:04:02 +0000 [thread overview]
Message-ID: <bug-83226-502-1TcEfqFrDI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83226-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83226
--- Comment #34 from nw9165-3201@yahoo.com ---
(In reply to Andy Furniss from comment #12)
> (In reply to John from comment #10)
> > I've applied the patches but I am not sure how to enable anything.
> > Since it's a drm patch, am I suppose to enable that the same way I do for
> > audio and dpm?
> > If so, I haven't tried, but I don't see anything in modinfo for csc.
>
> xrandr --verbose will show you the options/output name and the current
> setting.
>
> to change do something like -
>
> xrandr --output HDMI-0 --set output_csc tvrgb
Could anyone please explain why this setting needs to be done via xrandr?
Why not via the xorg.conf.d files?
To enable the TearFree option for example you can add:
Option "TearFree" "True"
inside a xorg.conf.d file for example.
So why can't the color range be set via a xorg.conf.d file like this for
example:
Option "Broadcast RGB" "Limited"
?
Why xrandr and not xorg.conf.d? Or why not both?
Also, why is the AMD driver's option being called:
xrandr --output $OUTPUT --set output_csc tvrgb
?
For the Intel driver it's called:
xrandr --output $OUTPUT --set "Broadcast RGB" "Limited"
Why does the setting have to have a different name between the AMD and Intel
driver?
Why can't the names just be kept the same?
Regards
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2470 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-05 14:04 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
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 [this message]
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-1TcEfqFrDI@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).