<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HDMI] No overscan properties" href="https://bugs.freedesktop.org/show_bug.cgi?id=29723#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HDMI] No overscan properties" href="https://bugs.freedesktop.org/show_bug.cgi?id=29723">bug 29723</a> from <a class="email" href="mailto:damien.lespiau@gmail.com" title="Damien Lespiau <damien.lespiau@gmail.com>"> Damien Lespiau</a> <pre>As far as I know, to support telling the sink to underscan CE modes, you need to have a video capability data block in the EDID telling you the sink can do that. For that you need the latest version of edid-decode with the patches I just pushed: <a href="http://cgit.freedesktop.org/xorg/app/edid-decode">http://cgit.freedesktop.org/xorg/app/edid-decode</a> For a samsung TV I have around: Extended tag: video capability data block YCbCr quantization: No Data (0) RGB quantization: No Data (0) PT scan behaviour: No Data (0) IT scan behaviour: Support both over- and underscan (3) CE scan behaviour: Support both over- and underscan (3) Your 4k TV doesn't have that, so overscans all CE modes. I think we'll need the panel fitter at that point. Now that's not as easy as it seems, the amount of overscan is not defined in the spec.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>