[Bug 94248] Can't get triple monitors working

[bugzilla-daemon at freedesktop.org]

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

--- Comment #58 from nw9165-3201 at yahoo.com ---
(In reply to Jani Nikula from comment #57)
> Generally speaking, installing/booting Windows should not be something that
> is required or recommended to get Linux working.

We were talking about getting potentially buggy firmware patched with the help
of Windows.

If the pre v1.36 HDMI firmware is buggy and needs to be updated to v1.36, then
it's just the way it is.

And if upgrading the HDMI firmware requires Windows because the manufacturer
has decided so, then that's also just the way it is (unless you figure out how
to make updating the firmware work on Linux).

(In reply to Jani Nikula from comment #57)
> It should not be part of
> the solution. Usually, it should also not be part of the debug process to
> compare to Windows. The drivers are completely different, and developed
> independently.

To me that sounds like "We have absolutely no idea what the completely
independent Windows driver team is doing to make three monitors working and we
haven't even attempted to ask them since... we work independently from each
other."

*facepalm*

I'd say it probably couldn't hurt to ask the Windows driver team. Maybe they
know something about the hardware that you don't.

And that's not a shame. But it would be a shame not to ask them.

(In reply to Jani Nikula from comment #57)> 
> There has to be thousands of products with Intel CPUs, from a huge number of
> OEMs with a huge number of chips from other vendors. The Linux driver
> developers probably have as much idea about what those OEMs do with the CPUs
> as we have about what you do with the driver and what other software you
> combine it with.

By the way:

Gigabyte also offers that MegaChips firmware update tool for their Z170
mainboards featuring HDMI 2.0, see "HDMI 2.0 FW Update Tool" over there:

http://www.gigabyte.com/support-downloads/Utility.aspx

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/20160618/a762a2a1/attachment.html>