Why does it insist that vesa timings are available before a new mode is
added? That leaves out digital screens. What’s the suggested
workaround/fix? Add phony timings?
Why does it insist that vesa timings are available before a new mode is
added? That leaves out digital screens. What’s the suggested
workaround/fix? Add phony timings?
Is there any way to tell if the kernel driver requires valid timings?
At the moment, the code assumes that the parameter to the FBIOPUT_VSCREENINFO
ioctl has to have valid timings to drive the monitor…
See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment