opensubscriber
   Find in this group all groups
 
Unknown more information…

d : dri-devel@lists.sourceforge.net 12 June 2008 • 2:47PM -0400

GEM merging to master
by Eric Anholt

REPLY TO AUTHOR
 
REPLY TO GROUP






We're getting close to ready to mark GEM on Intel as done.  We've got
one failing testcase that we isolated this week with interrupt handling,
and we've got a fix in testing that appears to be doing the job.

Tomorrow I'm planning on merging the GEM code to master of all 3
repositories.  At that point, I'll cut a branch called drm-ttm in drm
with the existing interface and support.  After that I'm planning on the
following changes:

1) Remove TTM code from i915.
We're going forward with GEM and not going to support two memory
managers in our driver.  GEM's got the features we need and equivalent
performance, with a simpler implementation.

2) Remove the existing TTM userland API.
Dave Airlie has requested this as it's expected that if the TTM kernel
implementation ends up being used by an open-source driver, it'll be
under device-specific ioctls.  This means things in installed *.h that
are TTM-specific, but not the guts of the kernel code.

3) Bump version to 2.4.0
We need a version to depend in the other repositories.  Because the
bufmgr code is now in libdrm, the 2d and mesa drivers will have a hard
requirement of this version of libdrm.  We expect that all open-source
platforms under consideration (linux, bsd, osol) that want to ship 2d
driver 2.4 will be able to ship libdrm 2.4.0.

4) Put out a release.
We're putting out the 2.4 (ugh, version number collision!) of the intel
2d driver in a month, and we need a libdrm with memory management that
is released and ready.

After I get at least 1-3 sorted out, I'll be working on 2d 2.4 release
process and putting together the kernel patch for submission to lkml.

--
Eric Anholt                             anholt@Free...
eric@anho...                         eric.anholt@inte...


Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.