From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0218146140==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 4B55F6E021 for ; Sun, 5 Jun 2016 14:04:02 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0218146140== Content-Type: multipart/alternative; boundary="14651354423.c32F8.21887"; charset="UTF-8" --14651354423.c32F8.21887 Date: Sun, 5 Jun 2016 14:04:02 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D83226 --- 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 f= or > > audio and dpm? > > If so, I haven't tried, but I don't see anything in modinfo for csc. >=20 > xrandr --verbose will show you the options/output name and the current > setting. >=20 > to change do something like - >=20 > 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --14651354423.c32F8.21887 Date: Sun, 5 Jun 2016 14:04:02 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 34 on bug 83226<= /a> from nw9165-3201&= #64;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 c=
sc.
>=20
> xrandr --verbose will show you the options/output name and the current
> setting.
>=20
> to change do something like -
>=20
> 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.
= --14651354423.c32F8.21887-- --===============0218146140== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0218146140==--