Comment # 10
on bug 69675
from Pierre Ossman
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > Something like this: > > > > Not really, the selection doesn't work like that - clock has to match > > exactly to the table value, it is not an upper bound. > > I just meant to patch the table so that you end up using the pre-defined > values for CTS and N rather than calculating them from the formula. > > { xxx, 11648, 210937, 17836, 234375, 11648, 140625 }, /* 74.25/1.001 MHz */ > > Replace xxx with whatever clock value the drm edid code gives you for > 74.25/1.001 MHz. > So what should I actually try for the second patch? What you wrote? Or the value from the mode line? :)
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
