[Bug 29723] [HDMI] No overscan properties

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29723

nw9165-3201 at yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chris at chris-wilson.co.uk,
                   |                            |jani.nikula at intel.com,
                   |                            |manasi.d.navare at intel.com,
                   |                            |ville.syrjala at linux.intel.c
                   |                            |om
            Version|7.5 (2009.10)               |unspecified
                 OS|Linux (All)                 |All
           Hardware|x86-64 (AMD64)              |All
             Status|NEEDINFO                    |NEW

--- Comment #18 from nw9165-3201 at yahoo.com ---
Any update on this one?

How do you properly compensate for overscan with the Intel driver, i.e. how do
you underscan?

There's a comment in a nouveau related bug saying:

> https://bugs.freedesktop.org/show_bug.cgi?id=47846#c1
> 
> Kernel 3.3 introduced underscan control
> 
> After updating, you can enable and adjust it using xrandr
> eg.
> xrandr --output HDMI-1 --set underscan on
> xrandr --output HDMI-1 --set "underscan hborder" 54 --set "underscan
> vborder" 51"

But that does not seem to work with the Intel driver.

When trying this on an i7-6700K running Ubuntu 16.04 + Oibaf PPA, i.e. with the
latest git snapshots of the graphics stack
(https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers), it results in
the following error message:

> X Error of failed request:  BadName (named color or font does not exist)
>   Major opcode of failed request:  140 (RANDR)
>   Minor opcode of failed request:  11 (RRQueryOutputProperty)
>   Serial number of failed request:  41
>   Current serial number in output stream:  41

Can someone please explain how to properly underscan?

Unfortunately there are still TVs out there which do now allow to disable
overscan, so it would be important to have an option to underscan via the
driver to compensate for the overscan.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161111/457a26ef/attachment.html>