Bug 16378

Summary: Driver vesa is broken with X Server 1.4 due to unresolved symbol xf86GTFMode
Product: xorg Reporter: Paulo César Pereira de Andrade <pcpa>
Component: Driver/VesaAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: brice.goglin, jan
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Paulo César Pereira de Andrade 2008-06-16 13:03:08 UTC
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  344)     for (v = mon->vrefresh[0].lo; v <= mon->vrefresh[0].hi; v++) {
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  345)      mode = xf86GTFMode(p->HDisplay, p->VDisplay, v, 0, 0);
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  346)      ret = xf86CheckModeForMonitor(mode, mon);
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  347)      xfree(mode);
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  348)      if (ret == MODE_OK)
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  349)          break;
99d2cc86 (Adam Jackson     2008-06-12 14:16:52 -0400  350)     }

Please add conditional code for 1.4 servers.
Comment 1 Brice Goglin 2008-07-04 17:36:21 UTC
mariodebian@gmail.com reported that replacing:
 	mode = xf86GTFMode(p->HDisplay, p->VDisplay, v, 0, 0);
with
	mode = xf86CVTMode(p->HDisplay, p->VDisplay, v, FALSE, FALSE);
when building against Xserver 1.4 seems to solve the problem. It seems to work fine here too.
Comment 2 Paulo César Pereira de Andrade 2009-02-02 11:38:37 UTC
  As Brice Goglin reported, it was possible
to use xf86CVTMode to correct the problem
for X Server 1.4.
  The solution used for Mandriva's packages,
before switching to X Server 1.5 or newer,
was to just revert the changes.

  Marking as WONTFIX as 1.4 should be no
longer the "mainstream" X Server for most/all
distros in "development state".

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.