[Bug 94248] Can't get triple monitors working

[bugzilla-daemon at freedesktop.org]

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

--- Comment #56 from nw9165-3201 at yahoo.com ---
(In reply to Manasi from comment #51)
> But
> the old firmware is possibly causing some issues. I might need to figure out
> a way to update the firmware version to v1.36.

Have you updated the firmware to v1.36 meanwhile?

And may I ask why you need to figure out a way to update the firmware?

I mean, judging from your email address, you are working at Intel?

Intel surely must have a copy and license for Windows lying around somewhere?

Then why not just boot into Windows and update the firmware and be done?

Or why not just contact ASRock and ask them how to update the firmware from
Linux? You work at Intel... can't be that hard to get in touch with board
manufacturers which utilize your hardware (Intel Z170)?

(In reply to Manasi from comment #54)
> Could you test this specific HDMI port next to
> native DP port on Windows? This will validate the hypothesis.

Sorry, but this really baffles me.

Why can't you test this yourself if you work at Intel?

It can't be too hard for someone at Intel to boot a PC into Windows?

Furthermore, it really baffled me that you didn't know that Z170 Skylake boards
which provide HDMI 2.0 are doing this by utilizing the MegaChips MCDP2800
LSPCON.

I mean, you work at the source, at Intel, there surely must be a way to gather
this info when working at Intel?

Also:

Is there no communication between the Windows driver team and the Linux driver
team at Intel?

Why can't you just contact someone on the Windows driver team at Intel and ask
him what they are doing to get three monitors working?

Maybe he can tell you and then you can do the same in Linux.

Regards

-- 
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/20160616/fe00bd75/attachment.html>