mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-24 08:28:16 +02:00
8771285054
Tungsten Graphics Inc. was acquired by VMware Inc. in 2008. Leaving the
old copyright name is creating unnecessary confusion, hence this change.
This was the sed script I used:
$ cat tg2vmw.sed
# Run as:
#
# git reset --hard HEAD && find include scons src -type f -not -name 'sed*' -print0 | xargs -0 sed -i -f tg2vmw.sed
#
# Rename copyrights
s/Tungsten Gra\(ph\|hp\)ics,\? [iI]nc\.\?\(, Cedar Park\)\?\(, Austin\)\?\(, \(Texas\|TX\)\)\?\.\?/VMware, Inc./g
/Copyright/s/Tungsten Graphics\(,\? [iI]nc\.\)\?\(, Cedar Park\)\?\(, Austin\)\?\(, \(Texas\|TX\)\)\?\.\?/VMware, Inc./
s/TUNGSTEN GRAPHICS/VMWARE/g
# Rename emails
s/alanh@tungstengraphics.com/alanh@vmware.com/
s/jens@tungstengraphics.com/jowen@vmware.com/g
s/jrfonseca-at-tungstengraphics-dot-com/jfonseca-at-vmware-dot-com/
s/jrfonseca\?@tungstengraphics.com/jfonseca@vmware.com/g
s/keithw\?@tungstengraphics.com/keithw@vmware.com/g
s/michel@tungstengraphics.com/daenzer@vmware.com/g
s/thomas-at-tungstengraphics-dot-com/thellstom-at-vmware-dot-com/
s/zack@tungstengraphics.com/zackr@vmware.com/
# Remove dead links
s@Tungsten Graphics (http://www.tungstengraphics.com)@Tungsten Graphics@g
# C string src/gallium/state_trackers/vega/api_misc.c
s/"Tungsten Graphics, Inc"/"VMware, Inc"/
Reviewed-by: Brian Paul <brianp@vmware.com>
44 lines
1.1 KiB
Text
44 lines
1.1 KiB
Text
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>
|