ffvertex: don't touch tex coords if coord replace is enabled.
[mesa.git] / src / gallium / auxiliary / util / u_simple_screen.h
1 /**************************************************************************
2 *
3 * Copyright 2009 VMware, Inc.
4 * All Rights Reserved.
5 *
6 * Permission is hereby granted, free of charge, to any person obtaining a
7 * copy of this software and associated documentation files (the
8 * "Software"), to deal in the Software without restriction, including
9 * without limitation the rights to use, copy, modify, merge, publish,
10 * distribute, sub license, and/or sell copies of the Software, and to
11 * permit persons to whom the Software is furnished to do so, subject to
12 * the following conditions:
13 *
14 * The above copyright notice and this permission notice (including the
15 * next paragraph) shall be included in all copies or substantial portions
16 * of the Software.
17 *
18 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
19 * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
20 * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
21 * IN NO EVENT SHALL TUNGSTEN GRAPHICS AND/OR ITS SUPPLIERS BE LIABLE FOR
22 * ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
23 * TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
24 * SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
25 *
26 **************************************************************************/
27
28 #ifndef U_SIMPLE_SCREEN_H
29 #define U_SIMPLE_SCREEN_H
30
31 #include "pipe/p_format.h"
32
33 struct pipe_screen;
34 struct pipe_fence_handle;
35 struct pipe_surface;
36 struct pipe_resource;
37
38 /**
39 * Gallium3D drivers are (meant to be!) independent of both GL and the
40 * window system. The window system provides a buffer manager and a
41 * set of additional hooks for things like command buffer submission,
42 * etc.
43 *
44 * There clearly has to be some agreement between the window system
45 * driver and the hardware driver about the format of command buffers,
46 * etc.
47 */
48 struct pipe_winsys
49 {
50 void (*destroy)( struct pipe_winsys *ws );
51
52 /** Returns name of this winsys interface */
53 const char *(*get_name)( struct pipe_winsys *ws );
54
55 /**
56 * Do any special operations to ensure buffer size is correct
57 */
58 void (*update_buffer)( struct pipe_winsys *ws,
59 void *context_private );
60 /**
61 * Do any special operations to ensure frontbuffer contents are
62 * displayed, eg copy fake frontbuffer.
63 */
64 void (*flush_frontbuffer)( struct pipe_winsys *ws,
65 struct pipe_surface *surf,
66 void *context_private );
67
68
69 /**
70 * Buffer management. Buffer attributes are mostly fixed over its lifetime.
71 *
72 * Remember that gallium gets to choose the interface it needs, and the
73 * window systems must then implement that interface (rather than the
74 * other way around...).
75 *
76 * usage is a bitmask of PIPE_BIND_*.
77 * All possible usages must be present.
78 *
79 * alignment indicates the client's alignment requirements, eg for
80 * SSE instructions.
81 */
82 struct pipe_resource *(*buffer_create)( struct pipe_winsys *ws,
83 unsigned alignment,
84 unsigned usage,
85 unsigned size );
86
87 /**
88 * Create a buffer that wraps user-space data.
89 *
90 * Effectively this schedules a delayed call to buffer_create
91 * followed by an upload of the data at *some point in the future*,
92 * or perhaps never. Basically the allocate/upload is delayed
93 * until the buffer is actually passed to hardware.
94 *
95 * The intention is to provide a quick way to turn regular data
96 * into a buffer, and secondly to avoid a copy operation if that
97 * data subsequently turns out to be only accessed by the CPU.
98 *
99 * Common example is OpenGL vertex buffers that are subsequently
100 * processed either by software TNL in the driver or by passing to
101 * hardware.
102 *
103 * XXX: What happens if the delayed call to buffer_create() fails?
104 *
105 * Note that ptr may be accessed at any time upto the time when the
106 * buffer is destroyed, so the data must not be freed before then.
107 */
108 struct pipe_resource *(*user_buffer_create)(struct pipe_winsys *ws,
109 void *ptr,
110 unsigned bytes);
111
112 /**
113 * Allocate storage for a display target surface.
114 *
115 * Often surfaces which are meant to be blitted to the front screen (i.e.,
116 * display targets) must be allocated with special characteristics, memory
117 * pools, or obtained directly from the windowing system.
118 *
119 * This callback is invoked by the pipe_screen when creating a texture marked
120 * with the PIPE_BIND_DISPLAY_TARGET flag to get the underlying
121 * buffer storage.
122 */
123 struct pipe_resource *(*surface_buffer_create)(struct pipe_winsys *ws,
124 unsigned width, unsigned height,
125 enum pipe_format format,
126 unsigned usage,
127 unsigned tex_usage,
128 unsigned *stride);
129
130
131 /**
132 * Map the entire data store of a buffer object into the client's address.
133 * flags is bitmask of PIPE_BUFFER_USAGE_CPU_READ/WRITE flags.
134 */
135 void *(*buffer_map)( struct pipe_winsys *ws,
136 struct pipe_resource *buf,
137 unsigned usage );
138
139 void (*buffer_unmap)( struct pipe_winsys *ws,
140 struct pipe_resource *buf );
141
142 void (*buffer_destroy)( struct pipe_resource *buf );
143
144
145 /** Set ptr = fence, with reference counting */
146 void (*fence_reference)( struct pipe_winsys *ws,
147 struct pipe_fence_handle **ptr,
148 struct pipe_fence_handle *fence );
149
150 /**
151 * Checks whether the fence has been signalled.
152 * \param flags driver-specific meaning
153 * \return zero on success.
154 */
155 int (*fence_signalled)( struct pipe_winsys *ws,
156 struct pipe_fence_handle *fence,
157 unsigned flag );
158
159 /**
160 * Wait for the fence to finish.
161 * \param flags driver-specific meaning
162 * \return zero on success.
163 */
164 int (*fence_finish)( struct pipe_winsys *ws,
165 struct pipe_fence_handle *fence,
166 unsigned flag );
167
168 };
169
170 /**
171 * The following function initializes a simple passthrough screen.
172 *
173 * All the relevant screen function pointers will forwarded to the
174 * winsys.
175 */
176 void u_simple_screen_init(struct pipe_screen *screen);
177
178 /**
179 * Returns the name of the winsys associated with this screen.
180 */
181 const char* u_simple_screen_winsys_name(struct pipe_screen *screen);
182
183 #endif