From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [PATCH 4/5] drm/i915: add 'rotation' CRTC property Date: Tue, 20 Mar 2012 20:49:13 +0200 Message-ID: <20120320184913.GX4917@intel.com> References: <1332254912-4352-1-git-send-email-przanoni@gmail.com> <1332254912-4352-4-git-send-email-przanoni@gmail.com> <4F68B4CE.8070407@stericsson.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTP id 39BAC9EB0A for ; Tue, 20 Mar 2012 11:41:45 -0700 (PDT) Content-Disposition: inline In-Reply-To: <4F68B4CE.8070407@stericsson.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Marcus Lorentzon Cc: Paulo Zanoni , "dri-devel@lists.freedesktop.org" List-Id: dri-devel@lists.freedesktop.org On Tue, Mar 20, 2012 at 05:48:14PM +0100, Marcus Lorentzon wrote: > Then it would also be nice to define some rules in KMS of what should be = > modeset params and what should be properties. Modeset params seems hard = > to add (struct change) and properties seems very loosely defined and = > device specific. Having something in between would be nice (standard and = > easy to add), to make it easier to add things like plane z-order = > (instead of driver specific ioctls or properties). > Maybe a new "atomic" modeset with just a list of {object_id, = > property_id, value} making all params into properties and modeset more = > dynamic. It would also solve the atomic modset, even with device = > specific properties and future features. Great minds think alike ;) Exactly what I've suggested a few times before. Unfortunately I haven't had the time to do any prototyping yet. -- = Ville Syrj=E4l=E4 Intel OTC