Attachment 126819 Details for Bug 95059 – Assume VX900 integrated TMDS transmitter presence patch to try 1

[patch] Assume VX900 integrated TMDS transmitter presence patch to try 1

Assume_VX900_Integrated_TMDS_Presence_to_Try_1.patch (text/plain), 1.32 KB, created by Kevin Brace on 2016-09-28 01:53:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Kevin Brace

Created: 2016-09-28 01:53:03 UTC

Size: 1.32 KB

patch

obsolete

>diff --git a/src/via_tmds.c b/src/via_tmds.c
>index 21b6cac..31b1bf0 100644
>--- a/src/via_tmds.c
>+++ b/src/via_tmds.c
>@@ -1048,23 +1048,8 @@ viaTMDSInit(ScrnInfoPtr pScrn)
>         xf86DrvMsg(pScrn->scrnIndex, X_INFO,
>                     "Integrated TMDS transmitter found via pin strapping.\n");
>     } else {
>-        /* 3X5.3E[5] supposedly signals the presence of
>-         * a DVI connector coming from an integrated TMDS transmitter.
>-         * This check is done if the pin strapping does not indicate
>-         * the presence of a DVI connector. Note that 3X5.3E is set by
>-         * VIA Technologies VGA BIOS. */
>-        cr3e = hwp->readCrtc(hwp, 0x3E);
>-        DEBUG(xf86DrvMsg(pScrn->scrnIndex, X_INFO,
>-                            "CR3E: 0x%02X\n", cr3e));
>-        if (cr3e & 0x20) {
>-            xf86DrvMsg(pScrn->scrnIndex, X_INFO,
>-                        "Integrated TMDS transmitter found via "
>-                        "VIA Technologies VGA BIOS scratch pad register.\n");
>-        } else {
>-            xf86DrvMsg(pScrn->scrnIndex, X_INFO,
>-                        "Integrated TMDS transmitter not found.\n");
>-            goto exit;
>-        }
>+        xf86DrvMsg(pScrn->scrnIndex, X_INFO,
>+                    "Assume integrated TMDS transmitter presence.\n");
>     }
> 
>     pVIATMDSRec = xnfcalloc(1, sizeof(VIATMDSRec));

Actions: View | Splinter Review

Attachments on bug 95059: 123138 | 123294 | 124119 | 124206 | 124207 | 125983 | 125984 | 126035 | 126741 | 126744 | 126745 | 126819 | 126834

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.