From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70934] [Regression] Problem with colors (depth?) on DCE5 Barts (HD69xx)
Date: Mon, 28 Oct 2013 08:56:01 +0000 [thread overview]
Message-ID: <bug-70934-502-xzLPJxMWUM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70934-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1210 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70934
--- Comment #8 from Rafał Miłecki <zajec5@gmail.com> ---
There is my EDID:
00ffffffffffff004ca333d000000000
0c150104952616780aa0558d515a962a
1c505400000001010101010101010101
0101010101016a4d80a07038fc413020
36007ed710000018d49a80a07038fc41
302036007ed710000038000000fc0053
414d53554e470a2020202020000000fc
00313733485430322d4330310a200035
0x12: 0x01 EDID version
0x13: 0x04 EDID revision
0x14: 0x95 Input
0x15: 0x26 Width [cm]
0x16: 0x16 Height [cm]
0x17: 0x78 Gamma
0x18: 0x0a Features
Let's take a look at that 0x95.
0x80 bit indicates that this is a digital signal interface
In this situation 0x70 bits store info about color depth.
0x10 indeed means 6 bits per color.
Btw I've noticed that when 0x80 bit is set we also should look at bits 0x18
from 0x18 (Features) to see supported color format(s).
My features bits are 0x0a which gives 0x0a & 0x18 = 0x8. That means my display
supports RGB 4:4:4 as well as YCbCr 4:4:4. But does it change anything?
Any other ideas? :|
This notebook is Samsung NP700G7A-S01PL
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2037 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:[~2013-10-28 8:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 21:01 [Bug 70934] New: [Regression] Problem with colors (depth?) on DCE5 Barts (HD69xx) bugzilla-daemon
2013-10-27 21:12 ` [Bug 70934] " bugzilla-daemon
2013-10-27 21:17 ` bugzilla-daemon
2013-10-27 21:20 ` bugzilla-daemon
2013-10-27 23:16 ` bugzilla-daemon
2013-10-27 23:17 ` bugzilla-daemon
2013-10-28 7:35 ` bugzilla-daemon
2013-10-28 7:35 ` bugzilla-daemon
2013-10-28 7:51 ` bugzilla-daemon
2013-10-28 8:56 ` bugzilla-daemon [this message]
2013-10-28 9:08 ` bugzilla-daemon
2013-10-28 9:08 ` bugzilla-daemon
2013-10-28 13:55 ` bugzilla-daemon
2013-10-28 15:07 ` bugzilla-daemon
2013-10-28 15:37 ` bugzilla-daemon
2013-10-28 17:56 ` bugzilla-daemon
2013-10-28 22:10 ` bugzilla-daemon
2013-10-29 6:21 ` bugzilla-daemon
2013-10-29 6:22 ` bugzilla-daemon
2013-10-29 15:05 ` bugzilla-daemon
2014-01-06 21:34 ` 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-70934-502-xzLPJxMWUM@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).