mesa/src/gallium/drivers/rbug
Marek Olšák 82db518f15 gallium: add external usage flags to resource_from(get)_handle (v2)
This will allow drivers to make better decisions about texture sharing
for DRI2, DRI3, Wayland, and OpenCL.

v2: add read/write flags, take advantage of __DRI_IMAGE_USE_BACKBUFFER

Reviewed-by: Axel Davy <axel.davy@ens.fr>
2016-03-09 15:02:25 +01:00
..
Makefile.am gallium/rbug: ship all files in the tarball 2014-09-05 23:46:26 +01:00
Makefile.sources gallium/rbug: ship all files in the tarball 2014-09-05 23:46:26 +01:00
rbug_context.c gallium: make pipe_context::begin_query return a boolean 2015-05-06 00:03:36 +03:00
rbug_context.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
rbug_core.c gallium: Replace u_simple_list.h with util/simple_list.h 2015-01-28 16:33:34 -08:00
rbug_objects.c gallium/drivers: Trivial code-style cleanup 2015-12-06 17:10:22 +01:00
rbug_objects.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
rbug_public.h gallium/drivers: Add extern "C" wrappers to public entry 2015-05-15 13:55:59 -04:00
rbug_screen.c gallium: add external usage flags to resource_from(get)_handle (v2) 2016-03-09 15:02:25 +01:00
rbug_screen.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
README s/Tungsten Graphics/VMware/ 2014-01-17 20:00:32 +00:00
SConscript rbug: consolidate C sources list into Makefile.sources 2013-10-01 07:29:49 -07:00

                              RBUG PIPE DRIVER


= About =

This directory contains a Gallium3D remote debugger pipe driver.
It provides remote debugging functionality.


= Usage =

Do

   GALLIUM_RBUG=true progs/trivial/tri

which should open gallium remote debugging session. While the program is running
you can launch the small remote debugging application from progs/rbug. More
information is in that directory. Also for a gui see:

   http://cgit.freedesktop.org/mesa/rbug-gui


= Integrating =

You can integrate the rbug pipe driver either inside the state tracker or the 
target. The procedure on both cases is the same. Let's assume you have a 
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):

  real_screen = real_screen_create(...);

The rbug screen is then created by doing

  rbug_screen = rbug_screen_create(real_screen);

You can then simply use rbug_screen instead of real_screen.

You can create as many contexts you wish from rbug_screen::context_create they
are automatically wrapped by rbug_screen.


--
Jose Fonseca <jfonseca@vmware.com>
Jakob Bornecrantz <jakob@vmware.com>