From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 20142] enabling underscan by default behaves badly with so many
monitors.
Date: Tue, 12 Oct 2010 15:10:16 GMT
Message-ID: <201010121510.o9CFAG0l027932@demeter2.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.sourceforge.net
To: dri-devel@lists.sourceforge.net
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=20142
Alex Deucher changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher 2010-10-12 15:10:14 ---
Unfortunately, there's no way for the driver to know whether the TV has
overscan enabled or not or if the TV is in some special scaling mode enabled.
Lots of TV's have no option to disable overscan. As such, the driver
underscans the image to compensate for the overscan; this is limited to the
common HD modes. Unfortunately, there's no good answer. Before I added
underscan support to the driver, I got bug reports from people with TV's where
the image was cut off on the edges due to the TV overscanning. You can disable
underscan in the driver with:
xrandr --output