a8f9936f55
Well, kinda. Strictly we prefer M_T_BUILTIN strongest since those are modes where the driver has said it absolutely can't do anything else (VBE). Then we look for user-defined modes, ie, modelines from the config file. Then we consider modes reported by the monitor via EDID. Finally if nothing has matched yet we consider the default mode pool. Within each of the above-mentioned classes, modes with the M_T_PREFERRED bit take priority over other modes in the same class. This logic ensures that the timings sent to the monitor exactly match the timings it reported as supported, which occasionally don't match the numbers you might get for that mode from CVT or GTF. |
||
|---|---|---|
| .. | ||
| darwin | ||
| dmx | ||
| kdrive | ||
| vfb | ||
| xfree86 | ||
| xgl | ||
| xnest | ||
| xprint | ||
| xwin | ||
| Makefile.am | ||