From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [PATCH 01/11] drm: add plane support Date: Mon, 31 Oct 2011 09:52:45 -0700 Message-ID: <20111031095245.7a95f59e@jbarnes-desktop> References: <1319536026-2877-1-git-send-email-jbarnes@virtuousgeek.org> <1319536026-2877-2-git-send-email-jbarnes@virtuousgeek.org> <20111025160945.5049568d@jbarnes-x220> <20111025194117.GG2894@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0619175964==" Return-path: Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [69.89.24.6]) by gabe.freedesktop.org (Postfix) with SMTP id 613029E86C for ; Mon, 31 Oct 2011 09:52:49 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Inki Dae Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0619175964== Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ZeMMRSCxYr0+Is1v.51KxqR"; protocol="application/pgp-signature" --Sig_/ZeMMRSCxYr0+Is1v.51KxqR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 31 Oct 2011 11:40:57 +0000 (UTC) Inki Dae wrote: > below is my simple idea. > 1. user requests buffer allocation with pixel format and resolution throu= gh=20 > gem framework. > 2. gem framework checks pixel format. > 3. specific gem framework allocates buffers as plane count according to t= he=20 > pixel format. (please, know that gem framework provides just interface so= =20 > acctual implementation would be done at specific gem framework) > 4. user gets the gem handle from gem framework. > 5. user sets the gem handle to specific drm framebuffer through=20 > drm_mode_addfb2 function. > 6. user requests setcrtc with fb id and crtc id. > 7. drm framework sets framebuffer(corresponding to fb id) to drm_mode_set. > 8. crtc calls set_config callbacks to configure hardware. > 9. specific crtc framework gets all buffers through framebuffer(actually,= it=20 > would be specific framebuffer)and sets them to overlay registers of hardw= are=20 > appropriately. >=20 >=20 > like this, how about using framebuffer and gem framework instead of plane= ? I'd=20 > be glad to give me your opinions. I'm not opposed to pushing the multi-object stuff into GEM instead, but I don't think step (9) will be enough to avoid having a separate plane object. Say the user passes in 3 RGB buffers. How do you know which one is the primary and which are overlays? Or are you saying the fb would have that information as well? If so, it would be a little harder to specify things like blending options or colorspace correction on a per-plane basis... But maybe I'm missing some part of things; do you have any patches to illustrate what you mean? I can see how it might work, but I don't know if it would be any simpler or cleaner than exposing plane objects. Thanks, --=20 Jesse Barnes, Intel Open Source Technology Center --Sig_/ZeMMRSCxYr0+Is1v.51KxqR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJOrtJdAAoJEIEoDkX4Qk9hvC8QAJ2bW+PDZzxcjhF9UA8UaP47 L5oikgdZBHZCczV+a5jlxjwtmOIlS556pRl+elrZD2pbCDgFMQP6y/BJqNtljo6q KSwGptmSNStkwlakVIiSWXwyo8Wb+8NkvPOKrCWbNt0v4w4IP5qqKyN5KdrHosIO pXIYfJ6q78N/wpK80f5PkNQ3LfiWlY3LukXf6lpcGkrcIbVkXHMJLjnMa6W99mM0 BpWzH3f5EsRCILSRsZ1NmW8Rx9FMW1GmxXxjqcMh4Zbt+cz/joVlHGIdUA+lZx94 tsfLiFNiwuPXgEb842tHA4fiKCZNtkac3wtiSkCC13T93QSmi6VMjhxIaCIAgoSo wDzEioXHMUM6FQFwLUgUmU1QzID9HyMByvHT4/3Pc0I0PXtKXewvFdGElshkB3Eu G0L6qEFIuZJ8OVshFVAgSp6CuC0vinpTfsFa8mK5x2LHU1T+Nq56w+SKSZvAJXxw J22egRMoTXDuyA4GALh5iJGjFiG50vKyLyn6O4CzT07wef7dzrFKMbMufzOESZkl BU2ZJjkZQ8pzOiF/9ifN1meXvwipDhCywyyrvWdK8ltOanNv9ci77srunUXKtske 3Rzg8xoDozx8v9gInFA2rKtHXCh8TGDW3wNG4RDNJ3UJWRjdVXs/4fxu3dWNSo1a XhJ1gLarem/nAvii+K4R =et+z -----END PGP SIGNATURE----- --Sig_/ZeMMRSCxYr0+Is1v.51KxqR-- --===============0619175964== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0619175964==--