From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thierry Reding Subject: Re: [RFCv3 12/14] drm: Specify cursor plane at CRTC initialization Date: Mon, 7 Apr 2014 12:05:52 +0200 Message-ID: <20140407100550.GE25718@ulmo> References: <1395188579-17191-1-git-send-email-matthew.d.roper@intel.com> <1395188579-17191-13-git-send-email-matthew.d.roper@intel.com> <20140328210409.GM22327@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1921777962==" Return-path: Received: from mail-bk0-f42.google.com (mail-bk0-f42.google.com [209.85.214.42]) by gabe.freedesktop.org (Postfix) with ESMTP id 8AF696E593 for ; Mon, 7 Apr 2014 03:06:42 -0700 (PDT) Received: by mail-bk0-f42.google.com with SMTP id mx12so630165bkb.29 for ; Mon, 07 Apr 2014 03:06:41 -0700 (PDT) In-Reply-To: <20140328210409.GM22327@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Daniel Vetter Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1921777962== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2qXFWqzzG3v1+95a" Content-Disposition: inline --2qXFWqzzG3v1+95a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 28, 2014 at 10:04:09PM +0100, Daniel Vetter wrote: > On Tue, Mar 18, 2014 at 05:22:57PM -0700, Matt Roper wrote: > > Add cursor plane as a parameter to drm_crtc_init() and update all > > existing DRM drivers to use a helper-provided primary plane. Passing > > NULL for this parameter indicates that there is no hardware cursor > > supported by the driver and no cursor plane should be provided to > > userspace. > >=20 > > Signed-off-by: Matt Roper >=20 > Ok, cursor planes. I've poked around in this a lot and unfortunately I > don't think we can achieve nirvana :( [...] > - For the pixel format I think it's ok to always assume RGBA. How so? We do have hardware on Tegra that doesn't support RGBA cursors and if at all possible I'd very much like to support that as well. New generations can do RGBA but still support the old pixel format. Having the option of supporting all formats would be nice. There was some discussion about implementing a bunch of plane properties so I think having one to enumerate a set of pixel formats wouldn't be such a big deal. Thierry --2qXFWqzzG3v1+95a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTQnh+AAoJEN0jrNd/PrOhiugP/3YNV9s+cKzB0Qwczd70GHHK Q0BSIYNsmwf1Wcs2MNiwG4xQqYQcOEJaYgzg2BkMqZHmMk1i8koXAq7ccJpc9VTp Wq/bAmVrDrGr20XhethZ94agSc+iRHnidocnzMbf43eMx/odj0hRhhzDyyzMiKPo DvXY87L6/SZfwO2asbInhuJXOX6qLsACuBvrOq+6lQ/VbkbCRD+EenZ/HZ4Bdhbc HKr2IMmUPnB6a+EphBkNdkBXTT35jfWQVJRrYV8jCG8e2pCKJ8A1ADsmqElKROus PKwzrIp8krIUmsFVB4wxkDRFHL0IMYXrFhf66QU5IBopjX69+DkdOjC5NL4MJpja WufN/aUjHTZQOb4Z6Akv6DNQwhej8PE4r5BWhN2KsB7UXdIJ7X8t4IqJyfBSpSRw tpUgG50wx7GxMwVlQIpGxtNjMdEoHOUE3XoC3vpkaEG7qGc0IwPOzRo2BeIjnvR1 osSmzNgYeIYEzAaR4zcXSkgG8NiRibdgpYDetTflwbyuI7nzArSyiEr+Yr5Aeqiw qPOfBNxgMeBKH1YpDHne2LJ3zmciHJPJC+OQZ9rx8q3tpmYdQQS8PF1Wom7Vx5BN MGrf2hrpgYzddLlyah/UMO2ViaezaxnTGVErKwVw02SZjSk5Z/1pEVcI8vAp+D+O x+s6CGkacd/bDmHhp2Zj =22F6 -----END PGP SIGNATURE----- --2qXFWqzzG3v1+95a-- --===============1921777962== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1921777962==--