crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Ville Syrjälä
On Tue, Apr 01, 2014 at 10:22:07AM -0400, Rob Clark wrote: > On Tue, Apr 1, 2014 at 10:12 AM, Ville Syrj?l? > wrote: > > On Tue, Apr 01, 2014 at 09:54:40AM -0400, Rob Clark wrote: > >> On Tue, Apr 1, 2014 at 9:40 AM, Daniel Vetter wrote: > >> > On Tue, Apr 01, 2014 at 08:40:54AM -0400, Rob Clark

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Ville Syrjälä
On Tue, Apr 01, 2014 at 09:54:40AM -0400, Rob Clark wrote: > On Tue, Apr 1, 2014 at 9:40 AM, Daniel Vetter wrote: > > On Tue, Apr 01, 2014 at 08:40:54AM -0400, Rob Clark wrote: > >> No, not really. I was just trying to get away with pushing some > >> complexity (for case #1) up to userspace inste

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Daniel Vetter
On Tue, Apr 01, 2014 at 08:40:54AM -0400, Rob Clark wrote: > No, not really. I was just trying to get away with pushing some > complexity (for case #1) up to userspace instead of doing it in the > kernel. To clarify: I don't think it makes sense to fully abstract this away in the kernel, especial

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Rob Clark
On Tue, Apr 1, 2014 at 10:42 AM, Ville Syrj?l? wrote: > On Tue, Apr 01, 2014 at 10:22:07AM -0400, Rob Clark wrote: >> On Tue, Apr 1, 2014 at 10:12 AM, Ville Syrj?l? >> wrote: >> > On Tue, Apr 01, 2014 at 09:54:40AM -0400, Rob Clark wrote: >> >> On Tue, Apr 1, 2014 at 9:40 AM, Daniel Vetter wrote

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Rob Clark
On Tue, Apr 1, 2014 at 10:12 AM, Ville Syrj?l? wrote: > On Tue, Apr 01, 2014 at 09:54:40AM -0400, Rob Clark wrote: >> On Tue, Apr 1, 2014 at 9:40 AM, Daniel Vetter wrote: >> > On Tue, Apr 01, 2014 at 08:40:54AM -0400, Rob Clark wrote: >> >> No, not really. I was just trying to get away with push

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Daniel Vetter
On Mon, Mar 31, 2014 at 02:04:00PM -0400, Rob Clark wrote: > I thought I'd kick off a thread to better discuss how to deal with > "large" displays which need multiple crtcs/planes merged to deal > without output larger than a certain width. > > What I have in mind basically amounts to driver-custo

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Rob Clark
On Tue, Apr 1, 2014 at 9:40 AM, Daniel Vetter wrote: > On Tue, Apr 01, 2014 at 08:40:54AM -0400, Rob Clark wrote: >> No, not really. I was just trying to get away with pushing some >> complexity (for case #1) up to userspace instead of doing it in the >> kernel. > > To clarify: I don't think it m

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Rob Clark
On Tue, Apr 1, 2014 at 8:40 AM, Rob Clark wrote: > On Tue, Apr 1, 2014 at 4:04 AM, Daniel Vetter wrote: >> On Mon, Mar 31, 2014 at 02:04:00PM -0400, Rob Clark wrote: >>> I thought I'd kick off a thread to better discuss how to deal with >>> "large" displays which need multiple crtcs/planes merged

crtc ganging in KMS, "large" displays, etc

2014-04-01 Thread Rob Clark
On Tue, Apr 1, 2014 at 4:04 AM, Daniel Vetter wrote: > On Mon, Mar 31, 2014 at 02:04:00PM -0400, Rob Clark wrote: >> I thought I'd kick off a thread to better discuss how to deal with >> "large" displays which need multiple crtcs/planes merged to deal >> without output larger than a certain width.

crtc ganging in KMS, "large" displays, etc

2014-03-31 Thread Rob Clark
I thought I'd kick off a thread to better discuss how to deal with "large" displays which need multiple crtcs/planes merged to deal without output larger than a certain width. What I have in mind basically amounts to driver-custom-properties and shouldn't really need much/anything in the way of dr