https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #3 from Kevin Brace <kevinbr...@gmx.com> ---
(In reply to HuangRan from comment #2)
Hi Frank,
> (In reply to Kevin Brace from comment #1)
> > Hi Frank,
> >
> > Interesting that the DRM or DDX is recognizing the HDMI monitor.
> >
> > ________________________________________________________________
> > . . .
> >
> > [ 91.005] (II) CHROME(0): EDID for output DVI-0
> > [ 91.005] (II) CHROME(0): Output VGA-0 disconnected
> > [ 91.005] (II) CHROME(0): Output HDMI-0 connected
> > [ 91.005] (II) CHROME(0): Output DVI-0 disconnected
> > [ 91.005] (II) CHROME(0): Using exact sizes for initial modes
> > [ 91.005] (II) CHROME(0): Output HDMI-0 using initial mode 1920x1080 +0+0
> > . . .
> > ________________________________________________________________
>
> Yup, Kevin. I see that. And I found EDID information is probed out by the
> driver. So we need see what happened that lead no display on the monitor.
>
> Thanks,
> Frank
The weird thing about VX900 chipset hardware programming documentation is that
it contains register information for DisplayPort, but not HDMI.
I do not know how James Simmons wrote the code, if the above assumption is
true.
That being said, VIA Technologies does have a quasi-open source 2D device
driver code on their website for Chrome 9 family.
http://download.viatech.com/en/support/driversSelect.jsp
Select "Linux (current)" and VX900 chipset.
At least for the DRM module which supports KMS, it is open source.
Check out via_chrome9_hdac_renew.c where it is apparently accessing the
registers related to HDMI.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
