All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 5/5] drm/edid: Parse and handle HDMI deep color modes.
Date: Thu, 22 May 2014 15:49:21 +0100	[thread overview]
Message-ID: <537E0E71.1060201@gmail.com> (raw)
In-Reply-To: <1400627871-18107-5-git-send-email-alexander.deucher@amd.com>

Alex Deucher wrote:
> From: Mario Kleiner <mario.kleiner.de@gmail.com>
>
> Check the HDMI cea block for deep color mode bits. If available,
> assign the highest supported bpc for a hdmi display, corresponding
> to the given deep color modes.

I haven't had time to test further, but with all 5 applied on top of 
deathsimple drm-fixes I loose output to TV as soon as I startx.

It worked in fbcon before starting X, but not switching vt after.

My TV according to edid-decode does support deep colour.

Nothing obvious to see in dmesg/Xorg.0.log and xrandr --verbose looked 
like it was on, tried some different modes, but nothing.

R9 270X

  reply	other threads:[~2014-05-22 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 23:17 [PATCH 1/5] drm/radeon: only apply hdmi bpc pll flags when encoder mode is hdmi Alex Deucher
2014-05-20 23:17 ` [PATCH 2/5] drm/radeon: fix pll setup for hdmi deep color Alex Deucher
2014-05-20 23:17 ` [PATCH 3/5] drm/radeon: Setup HDMI_CONTROL for hdmi deep color gcp's Alex Deucher
2014-05-21  5:58   ` Rafał Miłecki
2014-05-21 13:51     ` Alex Deucher
2014-05-21 13:58       ` Rafał Miłecki
2014-05-20 23:17 ` [PATCH 4/5] drm/radeon: Limit hdmi deep color bit depth to 12 bpc Alex Deucher
2014-05-20 23:17 ` [PATCH 5/5] drm/edid: Parse and handle HDMI deep color modes Alex Deucher
2014-05-22 14:49   ` Andy Furniss [this message]
2014-05-22 14:59     ` Alex Deucher

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=537E0E71.1060201@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.