summaryrefslogtreecommitdiff
path: root/lib/mesa/src/gallium/drivers/etnaviv/README
diff options
context:
space:
mode:
authorJonathan Gray <jsg@cvs.openbsd.org>2017-08-26 16:59:42 +0000
committerJonathan Gray <jsg@cvs.openbsd.org>2017-08-26 16:59:42 +0000
commit81ece42815e80818f160cdd85fab57d65b56ad15 (patch)
tree1059ff094da1aa50334115952fcb1cfcbda3acc6 /lib/mesa/src/gallium/drivers/etnaviv/README
parentb0244145d5bb49623d58f6b5cab8143ada692b60 (diff)
Revert to Mesa 13.0.6 to hopefully address rendering issues a handful of
people have reported with xpdf/fvwm on ivy bridge with modesetting driver.
Diffstat (limited to 'lib/mesa/src/gallium/drivers/etnaviv/README')
-rw-r--r--lib/mesa/src/gallium/drivers/etnaviv/README13
1 files changed, 0 insertions, 13 deletions
diff --git a/lib/mesa/src/gallium/drivers/etnaviv/README b/lib/mesa/src/gallium/drivers/etnaviv/README
deleted file mode 100644
index 58034b56e..000000000
--- a/lib/mesa/src/gallium/drivers/etnaviv/README
+++ /dev/null
@@ -1,13 +0,0 @@
-Notes for the etnaviv gallium driver
-------------------------------------
-
-There are two ways how this driver might get used:
-
-- application opens kms device (kmscube, weston, ..)
-- X via xf86-video-armada
-
-For the kms device case we provide a renderonly based driver like
-imx where all the magic for buffer import and export between kms
-and renderonly GPU is handled automaticly.
-
-For X/xf86-video-armada we need to provide etnaviv_dri.so.