From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH 0/1] HDMI 2.0 on CNL... not working...
Date: Fri, 10 Nov 2017 14:26:25 -0800 [thread overview]
Message-ID: <20171110222626.27212-1-rodrigo.vivi@intel.com> (raw)
I'm just sending this patch for reference here since
this is the patch that I believe it is the correct one
to get HDMI 2.0 working on CNL.
However I'm just getting a blank screen when trying to use
HDMI at 4k@60Hz here... Maybe it is just my bad old cable
here... maybe I'm missing something... but I couldn't stop
yet to collect logs...
Any feedback, idea, help is very welcome.
Thanks,
Rodrigo.
Rodrigo Vivi (1):
drm/i915/cnl: Extend HDMI 2.0 support to CNL.
drivers/gpu/drm/i915/intel_hdmi.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.13.6
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-11-10 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 22:26 Rodrigo Vivi [this message]
2017-11-10 22:26 ` [PATCH 1/1] drm/i915/cnl: Extend HDMI 2.0 support to CNL Rodrigo Vivi
2017-11-10 22:45 ` [PATCH] " Rodrigo Vivi
2017-11-10 23:50 ` [PATCH 1/1] " Manasi Navare
2017-11-11 0:04 ` Rodrigo Vivi
2017-11-11 9:47 ` Sharma, Shashank
2017-11-13 18:46 ` Rodrigo Vivi
2017-11-11 9:43 ` Sharma, Shashank
2017-11-13 18:47 ` Rodrigo Vivi
2017-11-15 19:05 ` David Weinehall
2017-11-17 13:09 ` Jani Nikula
2017-11-10 22:42 ` ✗ Fi.CI.BAT: failure for HDMI 2.0 on CNL... not working Patchwork
2017-11-10 23:17 ` ✓ Fi.CI.BAT: success for HDMI 2.0 on CNL... not working... (rev2) Patchwork
2017-11-11 1:13 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-12 23:29 ` [PATCH 0/1] HDMI 2.0 on CNL... not working Mike Lothian
2017-11-13 18:45 ` Rodrigo Vivi
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=20171110222626.27212-1-rodrigo.vivi@intel.com \
--to=rodrigo.vivi@intel.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 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.