search for: overscanned

https://bugs.freedesktop.org/show_bug.cgi?id=47846 Bug #: 47846 Summary: Nouveau -> overscan using HDMI Classification: Unclassified Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi, I have a GeForce 210-based video card hooked up to an LG monitor (IPS235P) via HDMI. At boot time, the video card displays an image on the monitor that is scaled down and surrounded by a black border approximately one inch in width. As far as I've been able to determine, this black border is caused by the video card attempting to compensate for any overscanning done by the monitor.

On Thu, Nov 22, 2018 at 12:23:29PM +0100, Boris Brezillon wrote: > @@ -924,6 +978,29 @@ struct drm_connector { > */ > struct drm_property_blob *path_blob_ptr; > > + /** > + * @underscan_mode_property: Optional connector underscan mode. Used by > + * the driver to scale the output image and compensate an overscan done > + * on the display side. > + */ > +

On Wed, Mar 05, 2014 at 12:40:34AM -0500, Ilia Mirkin wrote: > On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft <fehmarn-rund at ffti.de> wrote: > > I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the > > TV-Out. You can try nvtv (http://sourceforge.net/projects/nv-tv-out/). It bypasses X and modesetting and programs the Brooktree and CRTC directly. I've no

On Wed, Mar 05, 2014 at 12:46:04PM -0500, Ilia Mirkin wrote: > I actually checked this out last night, grabbed the BT869 datasheet. > Basically you'd have to implement something similar to the ch7006 > driver (see drivers/gpu/drm/i2c), which provides an API for setting > modes (the BT869 appears to have 8 of them, of which I'm guessing only > 4 are actually usable, probably

Boris Brezillon <boris.brezillon at bootlin.com> writes: > On Mon, 3 Dec 2018 16:40:11 +0200 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > >> On Thu, Nov 22, 2018 at 12:23:29PM +0100, Boris Brezillon wrote: >> > @@ -924,6 +978,29 @@ struct drm_connector { >> > */ >> > struct drm_property_blob *path_blob_ptr; >> >

Hi, Ilia Mirkin <imirkin at alum.mit.edu> [Mi, 05.03.2014 12:46]: > On Wed, Mar 5, 2014 at 6:06 AM, Dirk Thierbach <dthierbach at gmx.de> wrote: > > On Wed, Mar 05, 2014 at 12:40:34AM -0500, Ilia Mirkin wrote: > >> On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft <fehmarn-rund at ffti.de> wrote: > >> > I have here a GeForce 2MX (NV10) with a Brooktree

On Mon, May 07, 2018 at 04:44:32PM +0200, Boris Brezillon wrote: > We have 3 drivers defining the "underscan", "underscan hborder" and > "underscan vborder" properties (radeon, amd and nouveau) and we are > about to add the same kind of thing in VC4. > > Define generic underscan props and add new fields to the drm_connector > state so that the

On Wed, Mar 5, 2014 at 6:06 AM, Dirk Thierbach <dthierbach at gmx.de> wrote: > On Wed, Mar 05, 2014 at 12:40:34AM -0500, Ilia Mirkin wrote: >> On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft <fehmarn-rund at ffti.de> wrote: >> > I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the >> > TV-Out. > > You can try nvtv

Hello, This is an attempt at providing generic support for underscan connector props. We already have 3 drivers defining the same underscan, underscan vborder and underscan hborder properties (amd, radeon and nouveau) and I am about to add a new one, hence my proposal to put the prop parsing code in the core and add ->underscan fields to drm_connector_state. This v3 was based on the "VC4

https://bugs.freedesktop.org/show_bug.cgi?id=91411 Bug ID: 91411 Summary: TV hdmi output doesn't fit with desktop, minimize button(on windows) are missing, etc[NV50] Product: xorg Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority:

On Wed, Mar 5, 2014 at 2:57 PM, Nils Krafft <fehmarn-rund at ffti.de> wrote: > Hi, > > Ilia Mirkin <imirkin at alum.mit.edu> [Mi, 05.03.2014 12:46]: >> On Wed, Mar 5, 2014 at 6:06 AM, Dirk Thierbach <dthierbach at gmx.de> wrote: >> > On Wed, Mar 05, 2014 at 12:40:34AM -0500, Ilia Mirkin wrote: >> >> On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft

--- drivers/gpu/drm/i2c/ch7006_drv.c | 2 +- drivers/gpu/drm/i2c/ch7006_mode.c | 2 +- drivers/gpu/drm/i2c/ch7006_priv.h | 5 ++--- 3 files changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/i2c/ch7006_drv.c b/drivers/gpu/drm/i2c/ch7006_drv.c index c2594a1..7df4b86 100644 --- a/drivers/gpu/drm/i2c/ch7006_drv.c +++ b/drivers/gpu/drm/i2c/ch7006_drv.c @@ -351,7 +351,7

Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/i2c/ch7006_drv.c | 2 +- drivers/gpu/drm/i2c/ch7006_mode.c | 2 +- drivers/gpu/drm/i2c/ch7006_priv.h | 5 ++--- 3 files changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/i2c/ch7006_drv.c b/drivers/gpu/drm/i2c/ch7006_drv.c index c2594a1..7df4b86 100644 ---

We have 3 drivers defining the "underscan", "underscan hborder" and "underscan vborder" properties (radeon, amd and nouveau) and we are about to add the same kind of thing in VC4. Define generic underscan props and add new fields to the drm_connector state so that the property parsing logic can be shared by all DRM drivers. A driver can now attach underscan

On Mon, 3 Dec 2018 16:40:11 +0200 Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > On Thu, Nov 22, 2018 at 12:23:29PM +0100, Boris Brezillon wrote: > > @@ -924,6 +978,29 @@ struct drm_connector { > > */ > > struct drm_property_blob *path_blob_ptr; > > > > + /** > > + * @underscan_mode_property: Optional connector underscan mode. Used

Hello, This is an attempt at providing generic support for underscan connector props. We already have 3 drivers defining the same underscan, underscan vborder and underscan hborder properties (amd, radeon and nouveau) and I am about to add a new one, hence my proposal to put the prop parsing code in the core and add ->underscan fields to drm_connector_state. Note that I use this new

We have 3 drivers defining the "underscan", "underscan hborder" and "underscan vborder" properties (radeon, amd and nouveau) and we are about to add the same kind of thing in VC4. Define generic underscan props and add new fields to the drm_connector state so that the property parsing logic can be shared by all DRM drivers. A driver can now attach underscan

On Mon, May 07, 2018 at 05:15:33PM +0200, Daniel Vetter wrote: > On Mon, May 07, 2018 at 04:44:32PM +0200, Boris Brezillon wrote: > > We have 3 drivers defining the "underscan", "underscan hborder" and > > "underscan vborder" properties (radeon, amd and nouveau) and we are > > about to add the same kind of thing in VC4. > > > > Define

Dirk Thierbach <dthierbach at gmx.de> writes: >[...] >> The stuff about overscan/etc are exposed as KMS properties (which in >> turn appear in xrandr) and not specific to the BT869. > > The problem is that there's no good way to just say "I want this > overscan" and then get a valid set of register values, because of > the timing constraints. Nvtv