[Bug 94248] Can't get triple monitors working

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jul 26 18:29:18 UTC 2016


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

--- Comment #63 from Manasi <manasi.d.navare at intel.com> ---
Hi bz,

I have been working on rootcausing this issue. I have been also working with
ASRock to understand their HW architecture and which ports have LSPCON (DP to
HDMI active dongle). So till now we know for sure that the three ports on
ASRock board :
1. Native DP
2. LSPCON Port (Externally HDMI but internally DP with a LSPCON chip for
conversion)
3. Still trying to get more clarity on if it is native HDMI or 2nd LSPCON

I booted their system in Windows 10 and was able to upgrade the firmware to
v2.1 that has support for LSPCON as per talks with ASRock. At the same time we
(Intel) are adding support for LSPCON feature in our kernel and the patches are
being validated before merging into the kernel. I used these patches from our
developer and tested them on ASRock new firmware. With this the second port
that LSPCON has been validated and is working to generate a 4K display out. 
These patches will soon be merged and become part of the Linux kernel after
which you can pull them. You will need to upgrade the ASRock firmware and try
with the new kernel after they are merged. This should successfully generate
output on two monitors (connected to native DP and to the LSPCON port that is
HDMI Port located above native DP port). Because of LSPCON feature, you will
have no issues with these two ports and they would work cleanly. 

I am still in talks with ASRock to get clarity on why the third HDMI is not
working. The suspect is that the LSPCON chip on that port is not enabled by
ASRock in their firmware.

Manasi

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160726/d81a97ac/attachment.html>


More information about the intel-gfx-bugs mailing list