public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tom Horsley <horsley1953@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Really no way to get full RGB by default?
Date: Wed, 12 Feb 2014 19:05:09 -0500	[thread overview]
Message-ID: <20140212190509.1622bee9@zooty> (raw)
In-Reply-To: <20140212074425.30d06421@zooty>

> I built the latest git version of edid-decode,
> and I see it printing this info:
> 
>   Extended tag: video capability data block
>     YCbCr quantization: No Data (0)
>     RGB quantization: No Data (0)
> 
> If I toggle that "RGB quantization" bit (if I can figure
> out which byte it is in :-) will that be the magic
> that induces the intel driver to use full range RGB
> all the time?

I went ahead and tried that, and it didn't work, I
still get limited RGB by default, so I dug up the
kernel sources and started poking around and if I'm
reading them correctly, there is absolutely no way
to get full RGB by default if you are using a mode
that matches any of the standard CEA video modes.

Is this really correct?

Where's my kernel option to override this? :-).

Can we add a user defined extension to EDID to
change the default? (I have to override the EDID
on the kernel command line anyway to fix the
latest gnome stupidities).

Is there a program I could include in the initramfs
and change the setting really early? I certainly can't
run xrandr then.

I'm contemplating writing a program to hack
the built in table of CEA video modes in drm.ko so
the 1920x1080@60HZ won't match...

      reply	other threads:[~2014-02-13  0:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 12:44 EDID override for full RGB? Tom Horsley
2014-02-13  0:05 ` Tom Horsley [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=20140212190509.1622bee9@zooty \
    --to=horsley1953@gmail.com \
    --cc=intel-gfx@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