[Bug 80029] [bisected] HDMI Errors on drm-next & Linus's tree

[bugzilla-daemon@freedesktop.org]

[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=80029

--- Comment #16 from Mario Kleiner <mario.kleiner@tuebingen.mpg.de> ---
(In reply to comment #15)
> That indeed seems to have done the trick

Good. Can you test some sound output to your tv, to check if sound sounds
properly and not somehow distorted?

> 
> Is there a way to check that it's now using 36bit colour?

The fact that you get a functional display means it is using it. Before this
patch the gpu was signalling to your tv that it sends a dc36 signal, but it
wasn't sending a valid signal, so your tv couldn't decode properly. Now it
does.

Maybe there's also some deep color or 12 bpc indication in the onscreen display
somewhere?

A different question would be if the tv does something useful with the extra
bits, or just throws them away.

At the moment the patches would only affect the precision of the hardware gamma
tables, allowing to use their full output precision of 10 bits to get 2 extra
bits for gamma correction, so maybe color/gamma correction would produce a bit
less banding in some smooth color gradients. Our patches to enable a full 10
bit framebuffer didn't make it into drm-next or Linus tree so far, the pull
request is still pending, so i guess they won't make it into 3.16. And
userspace also needs work to enable full 10 bits, we have working patches but
they are not yet upstreamed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2349 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