similar to: [Bug 47846] New: Nouveau -> overscan using HDMI

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

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. > + */ > +

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

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. In this v2, I also converted the

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

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; >> >

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:

https://bugs.freedesktop.org/show_bug.cgi?id=43939 Bug #: 43939 Summary: DVI monitor connected via HDMI is blank / standby (NV96 / 9500GS) Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal

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 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

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 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

Hi Boris, Just because I happened to read the docs in here, one typo below: On Thu, Nov 22, 2018 at 12:23:29PM +0100, 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

On 2018-05-07 12:19 PM, Boris Brezillon wrote: > On Mon, 7 May 2018 18:01:44 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> 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

On Fri, May 11, 2018 at 07:12:21PM +0200, Boris Brezillon wrote: > On Fri, 11 May 2018 19:54:02 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > > On Fri, May 11, 2018 at 05:52:56PM +0200, Boris Brezillon wrote: > > > On Fri, 11 May 2018 18:34:50 +0300 > > > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > >

On Fri, May 11, 2018 at 04:59:17PM +0200, Boris Brezillon wrote: > Applying an underscan setup is just a matter of scaling all planes > appropriately and adjusting the CRTC X/Y offset to account for the > horizontal and vertical border. > > Create an vc4_plane_underscan_adj() function doing that and call it from > vc4_plane_setup_clipping_and_scaling() so that we are ready to

On Fri, May 11, 2018 at 05:52:56PM +0200, Boris Brezillon wrote: > On Fri, 11 May 2018 18:34:50 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > > On Fri, May 11, 2018 at 04:59:17PM +0200, Boris Brezillon wrote: > > > Applying an underscan setup is just a matter of scaling all planes > > > appropriately and adjusting the CRTC X/Y offset to

On Mon, May 07, 2018 at 04:44:34PM +0200, Boris Brezillon wrote: > Now that the plane code takes the underscan setup into account, we can > safely attach the underscan props to the HDMI connector. > > We also take care of filling AVI infoframes correctly to expose the > top/botton/left/right bar. > > Note that these underscan props match pretty well the >

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 Fri, May 11, 2018 at 09:47:49PM +0200, Boris Brezillon wrote: > On Fri, 11 May 2018 20:29:48 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > > On Fri, May 11, 2018 at 07:12:21PM +0200, Boris Brezillon wrote: > > > On Fri, 11 May 2018 19:54:02 +0300 > > > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > >