Go to file
Chris Forbes 20c5607b57 intel: fix length mask for Gen5/Gen6 3DSTATE_CLEAR_PARAMS
On Gen6, bit 15 is now `Depth Clear Value Valid`. This was being treated
as part of the length, and failing the rest of the batchbuffer decode.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
2013-02-06 11:20:05 -08:00
exynos libdrm/exynos: padding gem_mmap structure to 64-bit aligned 2012-07-06 16:36:31 +02:00
include intel: Import updated i915_drm.h. 2012-08-10 09:48:05 -07:00
intel intel: fix length mask for Gen5/Gen6 3DSTATE_CLEAR_PARAMS 2013-02-06 11:20:05 -08:00
libkms libkms: return -EINVAL on fstat error 2013-01-02 10:57:07 -05:00
m4 build: Update autotools configuration 2011-03-21 13:43:43 +00:00
man man: Fix typo and use $() for make expressions 2013-01-25 13:46:57 -08:00
nouveau nouveau: use @PACKAGE_VERSION@ in libdrm_nouveau.pc 2013-01-16 14:29:35 +01:00
omap omap: release lock also on error paths 2012-10-09 09:41:27 -05:00
radeon radeon: add OLAND pci ids 2013-02-04 15:03:55 -05:00
tests configure.ac: Allow forcible disabling of Cairo support 2012-10-08 15:49:23 +10:00
.gitignore man: fix manpage build instructions 2013-01-16 10:59:14 -08:00
Makefile.am libdrm: remove DISTCHECK_CONFIGURE_FLAGS 2013-02-05 14:14:01 +01:00
README Update README 2009-11-20 17:08:28 -05:00
RELEASING Add RELEASING to document the release process 2009-12-03 17:50:37 -05:00
autogen.sh autogen.sh: Restore passing --enable-maintainer-mode to configure. 2012-06-08 15:23:46 +02:00
configure.ac configure.ac: bump version to 2.4.42 for release 2013-02-05 14:14:01 +01:00
libdrm.pc.in Revert "Fix pkgconfig includes for /usr/include/drm" 2010-04-09 16:33:38 -04:00
libdrm_lists.h lists: add nicer+unsafe foreach, and list join macros 2012-04-14 02:47:04 +10:00
xf86atomic.h Correct the Solaris definitions of atomic_add & atomic_dec 2010-04-16 17:37:58 -07:00
xf86drm.c libdrm: add prime fd->handle and handle->fd interfaces 2012-07-16 02:39:56 +01:00
xf86drm.h libdrm: add prime fd->handle and handle->fd interfaces 2012-07-16 02:39:56 +01:00
xf86drmHash.c Move libdrm/ up one level 2009-11-17 11:15:06 -05:00
xf86drmMode.c initialize width/height fields in drmModeCrtc 2012-10-14 16:56:53 -05:00
xf86drmMode.h Add support for generic object properties IOCTLs 2012-06-08 09:27:20 -05:00
xf86drmRandom.c Move libdrm/ up one level 2009-11-17 11:15:06 -05:00
xf86drmSL.c Tidy up compile warnings by cleaning up types. 2010-02-04 19:45:10 -05:00
xf86mm.h Move libdrm/ up one level 2009-11-17 11:15:06 -05:00

README

libdrm - userspace library for drm

This  is libdrm,  a userspace  library for  accessing the  DRM, direct
rendering  manager, on  Linux,  BSD and  other  operating systes  that
support the  ioctl interface.  The library  provides wrapper functions
for the  ioctls to avoid  exposing the kernel interface  directly, and
for chipsets with drm memory manager, support for tracking relocations
and  buffers.   libdrm  is  a  low-level library,  typically  used  by
graphics drivers  such as the Mesa  DRI drivers, the  X drivers, libva
and  similar projects.  New  functionality in  the kernel  DRM drivers
typically requires  a new  libdrm, but a  new libdrm will  always work
with an older kernel.


Compiling
---------

libdrm  is  a  standard  autotools  packages and  follows  the  normal
configure, build  and install steps.   The first step is  to configure
the package, which is done by running the configure shell script:

	./configure

By default, libdrm  will install into the /usr/local/  prefix.  If you
want  to  install   this  DRM  to  replace  your   system  copy,  pass
--prefix=/usr and  --exec-prefix=/ to configure.  If  you are building
libdrm  from a  git checkout,  you first  need to  run  the autogen.sh
script.  You can  pass any options to autogen.sh  that you would other
wise  pass to configure,  or you  can just  re-run configure  with the
options you need once autogen.sh finishes.

Next step is to build libdrm:

	make

and once make finishes successfully, install the package using

	make install

If you are install into a system location, you will need to be root to
perform the install step.