linux-kernel - Re: [PATCH] drm: Add GEM ("graphics execution manager") to i915 driver.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1217614310.23437.251.camel@koto.keithp.com>
Date:	Fri, 01 Aug 2008 11:11:50 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	keithp@...thp.com, Eric Anholt <eric@...olt.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm: Add GEM ("graphics execution manager") to i915
	driver.

On Fri, 2008-08-01 at 08:44 -0700, Randy Dunlap wrote:

> "the 2d driver" ... "the 3d driver".
> Just curious:  Is there only one of each of these?

We only need one X.org 2D and one Mesa 3D driver for each card, but DRI
supports as many rendering APIs as you like, including XvMC which offers
accelerated video decode on top of DRI as well.

So, the answer is that yes, at this point, we have only the two Intel
integrated graphics drivers using GEM, but also no, the interface can
support as many drivers as you want.

I hope that GEM will encourage more graphics API research as it allows
multiple user-space APIs to talk to the same underlying hardware
resources.

-- 
keith.packard@...el.com

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)