Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Mon, Nov 07, 2016 at 03:46:52PM +, Russell King - ARM Linux wrote: > On Mon, Nov 07, 2016 at 04:09:09PM +0100, Maxime Ripard wrote: > > Hi Russell, > > > > On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > > > Yes. And that is an XBMC only solution, that doesn't

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Mon, Nov 07, 2016 at 03:46:52PM +, Russell King - ARM Linux wrote: > On Mon, Nov 07, 2016 at 04:09:09PM +0100, Maxime Ripard wrote: > > Hi Russell, > > > > On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > > > Yes. And that is an XBMC only solution, that doesn't

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Mon, Nov 07, 2016 at 04:09:09PM +0100, Maxime Ripard wrote: > Hi Russell, > > On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > > Yes. And that is an XBMC only solution, that doesn't work with the > > > fbdev emulation and is probably doing an additional composition

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Mon, Nov 07, 2016 at 04:09:09PM +0100, Maxime Ripard wrote: > Hi Russell, > > On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > > Yes. And that is an XBMC only solution, that doesn't work with the > > > fbdev emulation and is probably doing an additional composition

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > Yes. And that is an XBMC only solution, that doesn't work with the > > fbdev emulation and is probably doing an additional composition to > > scale down and center their frames through OpenGL. > > Well, it

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Thu, Nov 03, 2016 at 09:54:45AM +, Russell King - ARM Linux wrote: > > Yes. And that is an XBMC only solution, that doesn't work with the > > fbdev emulation and is probably doing an additional composition to > > scale down and center their frames through OpenGL. > > Well, it

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Sean, On Thu, Nov 03, 2016 at 03:11:26PM -0600, Sean Paul wrote: > On Thu, Nov 3, 2016 at 3:01 AM, Maxime Ripard > wrote: > > Hi Russell, > > > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > >> On Tue, Oct 18, 2016 at 12:03:49PM

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Sean, On Thu, Nov 03, 2016 at 03:11:26PM -0600, Sean Paul wrote: > On Thu, Nov 3, 2016 at 3:01 AM, Maxime Ripard > wrote: > > Hi Russell, > > > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > >> On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > >>

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Thu, Nov 3, 2016 at 3:01 AM, Maxime Ripard wrote: > Hi Russell, > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: >> On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: >> > The first one is that this overscanning should

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Thu, Nov 3, 2016 at 3:01 AM, Maxime Ripard wrote: > Hi Russell, > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: >> On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: >> > The first one is that this overscanning should be reported by the >> > connector

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Thu, Nov 03, 2016 at 10:01:06AM +0100, Maxime Ripard wrote: > Hi Russell, > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > > On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > > > The first one is that this overscanning should be reported by the > >

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Thu, Nov 03, 2016 at 10:01:06AM +0100, Maxime Ripard wrote: > Hi Russell, > > On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > > On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > > > The first one is that this overscanning should be reported by the > >

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > > The first one is that this overscanning should be reported by the > > connector I guess? but this is really TV specific, so we need one way >

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Mon, Oct 31, 2016 at 08:42:34AM +, Russell King - ARM Linux wrote: > On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > > The first one is that this overscanning should be reported by the > > connector I guess? but this is really TV specific, so we need one way >

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > The first one is that this overscanning should be reported by the > connector I guess? but this is really TV specific, so we need one way > to let the user tell how the image is displayed on its side, and we > cannot really

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, Oct 18, 2016 at 12:03:49PM +0200, Maxime Ripard wrote: > The first one is that this overscanning should be reported by the > connector I guess? but this is really TV specific, so we need one way > to let the user tell how the image is displayed on its side, and we > cannot really

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, 18 Oct 2016 12:03:49 +0200 Maxime Ripard wrote: > The fourth one being the major one. Every time I raised the issue on > IRC, the answer basically was "we don't care about analog", so I'm a > bit pessimistic about whether dealing with this in the core

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, 18 Oct 2016 12:03:49 +0200 Maxime Ripard wrote: > The fourth one being the major one. Every time I raised the issue on > IRC, the answer basically was "we don't care about analog", so I'm a > bit pessimistic about whether dealing with this in the core would be > accepted, hence why I

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Tue, Oct 18, 2016 at 10:24:22AM +0100, Russell King - ARM Linux wrote: > On Tue, Oct 18, 2016 at 10:29:33AM +0200, Maxime Ripard wrote: > > The Allwinner display engine doesn't have any kind of hardware help to deal > > with TV overscan. > > I'm not sure I follow. My

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

Hi Russell, On Tue, Oct 18, 2016 at 10:24:22AM +0100, Russell King - ARM Linux wrote: > On Tue, Oct 18, 2016 at 10:29:33AM +0200, Maxime Ripard wrote: > > The Allwinner display engine doesn't have any kind of hardware help to deal > > with TV overscan. > > I'm not sure I follow. My

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, Oct 18, 2016 at 10:29:33AM +0200, Maxime Ripard wrote: > The Allwinner display engine doesn't have any kind of hardware help to deal > with TV overscan. I'm not sure I follow. My understanding (from reading the CEA specs) is that TVs are expected to overscan the image, so the upper left,

Re: [PATCH 0/5] drm/sun4i: Handle TV overscan

On Tue, Oct 18, 2016 at 10:29:33AM +0200, Maxime Ripard wrote: > The Allwinner display engine doesn't have any kind of hardware help to deal > with TV overscan. I'm not sure I follow. My understanding (from reading the CEA specs) is that TVs are expected to overscan the image, so the upper left,

[PATCH 0/5] drm/sun4i: Handle TV overscan

Hi, The Allwinner display engine doesn't have any kind of hardware help to deal with TV overscan. This means that if we use the only mode the hardware provides (either PAL or NTSC, or something else), most of the screens will crop the borders of the image, which is bad. We can however use

[PATCH 0/5] drm/sun4i: Handle TV overscan

Hi, The Allwinner display engine doesn't have any kind of hardware help to deal with TV overscan. This means that if we use the only mode the hardware provides (either PAL or NTSC, or something else), most of the screens will crop the borders of the image, which is bad. We can however use