gallium: Expose a opaque winsys handle and functions on pipe_screen
authorJakob Bornecrantz <jakob@vmware.com>
Mon, 15 Feb 2010 17:17:30 +0000 (17:17 +0000)
committerJakob Bornecrantz <jakob@vmware.com>
Mon, 1 Mar 2010 16:05:24 +0000 (16:05 +0000)
commitb2e94d05c9602e2814a513a51eed67d014b338f3
treeed1b442663384771a7060847dfdba85d439b7bb4
parentf54aecc4f2e83babd1883c2bbd0bba6906cdab07
gallium: Expose a opaque winsys handle and functions on pipe_screen

Instead of having these functions on a side interface like on
drm_api create a opaque winsys_handle that is to be passed down
into the winsys.

Currently the only thing ported to this new interface is drm_api,
and of that only the components that builds by default is ported.
All the drivers and any extra state trackers needs to be ported
before this can go into master.
src/gallium/drivers/identity/id_drm.c
src/gallium/drivers/identity/id_screen.c
src/gallium/drivers/trace/tr_drm.c
src/gallium/drivers/trace/tr_screen.c
src/gallium/include/pipe/p_screen.h
src/gallium/include/state_tracker/drm_api.h
src/gallium/state_trackers/dri/dri_drawable.c
src/gallium/state_trackers/egl/x11/native_dri2.c
src/gallium/state_trackers/xorg/xorg_crtc.c
src/gallium/state_trackers/xorg/xorg_dri2.c
src/gallium/state_trackers/xorg/xorg_driver.c