<div dir="ltr">Hello Joshua,<div><br></div><div>You managed to confuse me, on the very high level.Why, you'll ask?</div><div><br></div><div>[1] I have no idea if you ever were able to solve the following issue: <a href="https://www.mail-archive.com/coreboot@coreboot.org/msg48827.html">https://www.mail-archive.com/coreboot@coreboot.org/msg48827.html</a> And did you, after all (and what was the solution, if not secret)?</div><div>[2] It seems that you in your original email imply that Linux GFX driver i915 is used in WIN10 too? Or Linux is actually host, and WIN10 is a VM on the top of some (which one?) HYP type 2? Or maybe, HYP is type 1? Really, what is the true OS configuration stack in your case???</div><div><br></div><div><p class="MsoNormal" style="font-size:12.8px">Any answer would be greatly appreciated. <br></p><p class="MsoNormal" style="font-size:12.8px"> </p><p class="MsoNormal" style="font-size:12.8px">Thanks,<br></p><p class="MsoNormal" style="font-size:12.8px">ZS</p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 11, 2017 at 10:43 PM, Joshua Pincus <span dir="ltr"><<a href="mailto:joshua.pincus@gmail.com" target="_blank">joshua.pincus@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<p class="MsoNormal">Hey Folks,</p><p class="MsoNormal"><br></p><p class="MsoNormal">I've been smacking my head against the wall for 2 weeks. I can't smack it anymore. There's not much brain left at this point. Here's my issue:<br></p><p class="MsoNormal"><br></p><p class="MsoNormal">I have a Broadwell system with HD Video/Audio support.
When Windows 10 runs native (without a Hypervisor), Windows correctly finds the
DisplayPort adapter and correctly probes whatever it is that it needs to probe
to determine that the adapter in question supports both audio and video
output. When Windows 10 is executed as a guest on top of a Hypervisor, it
correctly finds both the video device @ 0/2/0 and the audio device @ 0/3/0 but
it is unable to detect that the DisplayPort supports audio. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I can confirm that both the Intel drivers for video and
audio correctly attach and seem to be running perfectly inside the guest VM.
All of the PCI BARs associated with both devices are correctly being mapped to
the Windows 10 guest. It is my guess that Windows is looking at something
other than the EDID extracted from the attached monitor or the MMIO BAR for the
PCI audio or video devices to determine that audio is supported by the attached
hardware. Indeed, if I probe the EDID information from the guest, I see
that the attached monitor supports audio. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">My question is this: Is there something else other than the PCI BARs
associated with the onboard HD graphics and HD audio devices that are required
for a Windows or a Linux guest to detect the physical presence of audio
hardware associated with an attached monitor via HDMI or DP? Is there an
MCH or PCH register? My guess is that I am not mapping ALL of the BARs or
IO ports into the guest to allow Windows to probe the hardware properly.
Something is missing. I can’t figure out what that something is.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Any help would be
greatly appreciated. <br></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,<br></p>
<p class="MsoNormal">JP </p>
</div>
<br>--<br>
coreboot mailing list: <a href="mailto:coreboot@coreboot.org">coreboot@coreboot.org</a><br>
<a href="https://mail.coreboot.org/mailman/listinfo/coreboot" rel="noreferrer" target="_blank">https://mail.coreboot.org/<wbr>mailman/listinfo/coreboot</a><br></blockquote></div><br></div>