Please note that libdrm now has a 1.0 branch. If you make changes to the DRM headers like the recent via_drm.h updates, such that drivers will need them to build, make sure they are applied to the 1.0 branch as well.
A rough roadmap for libdrm 1.1: - Build and install the test apps by default - Add xdriinfo to the test app suite - Additional API for unified memory manager (see http://dri.freedesktop.org/wiki/DriMemoryManagerDesign for proposal) - Any changes needed to enable the XvMC drivers to link against libdrm (I don't expect there's much to do here) - Header cleanup (see below) - Unify libdrm code paths between client and server The motivation for that last one is so the remaining copy of libdrm in the server module can be dropped, and libdrm can finally move to being a fully shared object. Regarding header cleanup: Dave has said that the only headers libdrm should be installing are drm.h, drm_sarea.h, and *_drm.h for each device. r300 and via violate this rule and also install headers with register defines. I don't see why they need that, given that the others don't. I'd like to come up with a real policy here. - ajax
pgpGYGG5pohCo.pgp
Description: PGP signature
