Dave Airlie wrote: > Hi Thomas, > > I've made some changes you might be interested in on the > modesetting-gem branch of the main repo. > > 1. removed all the TTM interfaces and ioctls from the kernel API. > 2. removed drm_bo_lock.c (we need to discuss what we want that for) > 3. built a radeon GEM interface on top of the TTM internals. > 4. added clean flag for buffers that get migrated to VRAM immediately. > - with pixmaps we have no idea of the usage pattern usually at create time, > however if nothing has ever mapped the bo and nothing has ever > moved it then > we can optimise the first move to VRAM away and just memset/solid > fill the VRAM area to 0. > > I'm hoping the radeon interface is nearly good enough for a 3D driver > to use, which would allow some cleanup of > the kernel internals. > > Dave. > Dave, This all sounds good.
The drm_bo_lock.c is intended to replace the drm hardware lock on VT switches when the X server wants to clean all memory for release to a legacy fbdev driver. It will block all drm clients trying to put a buffer in video memory, and basically stall them until the X server is switched back in, in which case the X server will: 1) release the bo_lock allowing for clients to start rendering to private buffers. b) allocate and set up its new front buffer c) release the DRM hardware lock, allowing for clients to access the SAREA and thus the new front buffer. I'm not sure how this fits into the modesetting world. Perhaps the need for it will go away, but for largely lockless legacy DRI solutions (where the lock only protects the SAREA) it's needed. /Thomas ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
