[Bug 97971] Reading EDID on valleyview(device id: 0x0f31) fails

[bugzilla-daemon at freedesktop.org]

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

Ville Syrjala <ville.syrjala at linux.intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #8 from Ville Syrjala <ville.syrjala at linux.intel.com> ---
(In reply to Jani Nikula from comment #5)
> 杨波, can you get /sys/kernel/debug/dri/0/i915_vbt or
> /sys/kernel/debug/dri/0/i915_opregion from the original reporter?
> 
> Ville, any idea if we should be looking at some other ddc pin in the VBT, or
> is the IS_VALLEYVIEW() thing all right? Are there any machines that would
> have both VGA and DVI connectors, or does having DVI always mean that the
> VGA is routed to DVI-I?

I didn't realize we even had machines with DVI-I. I've only ever seen separate
DVI-D + VGA myself.

I would be rather surprised if there's a VLV machine with DVI-I. But who knows,
I've been known to be wrong occasionally. So the key question here is; Does the
machine have DVI-I, or just HDMI/DVI-D using non-standard DDC pins?

As far as finding the right DDC pin goes, I think VBT has both the global CRT
DDC pin, and the per-child device DDC pin. We only look at the global thing I
believe. Dunno if we should be looking at the other one.

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