1 /**************************************************************************
3 * Copyright 2007 Tungsten Graphics, Inc., Cedar Park, Texas.
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:
14 * The above copyright notice and this permission notice (including the
15 * next paragraph) shall be included in all copies or substantial portions
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.
26 **************************************************************************/
30 * This is the interface that i915simple requires any window system
31 * hosting it to implement. This is the only include file in i915simple
40 #include "pipe/p_defines.h"
43 /* Pipe drivers are (meant to be!) independent of both GL and the
44 * window system. The window system provides a buffer manager and a
45 * set of additional hooks for things like command buffer submission,
48 * There clearly has to be some agreement between the window system
49 * driver and the hardware driver about the format of command buffers,
53 struct pipe_buffer_handle
;
59 * Additional winsys interface for i915simple.
61 * It is an over-simple batchbuffer mechanism. Will want to improve the
62 * performance of this, perhaps based on the cmdstream stuff. It
63 * would be pretty impossible to implement swz on top of this
66 * Will also need additions/changes to implement static/dynamic
72 * Reserve space on batch buffer.
74 * Returns a null pointer if there is insufficient space in the batch buffer
75 * to hold the requested number of dwords and relocations.
77 * The number of dwords should also include the number of relocations.
79 unsigned *(*batch_start
)( struct i915_winsys
*sws
,
83 void (*batch_dword
)( struct i915_winsys
*sws
,
87 * Emit a relocation to a buffer.
89 * Used not only when the buffer addresses are not pinned, but also to
90 * ensure refered buffers will not be destroyed until the current batch
91 * buffer execution is finished.
93 * The access flags is a combination of I915_BUFFER_ACCESS_WRITE and
94 * I915_BUFFER_ACCESS_READ macros.
96 void (*batch_reloc
)( struct i915_winsys
*sws
,
97 struct pipe_buffer_handle
*buf
,
98 unsigned access_flags
,
102 * Flush the batch buffer.
104 * Fence argument must point to NULL or to a previous fence, and the caller
105 * must call fence_reference when done with the fence.
107 void (*batch_flush
)( struct i915_winsys
*sws
,
108 struct pipe_fence
**fence
);
113 void (*fence_reference
)( struct i915_winsys
*sws
,
114 struct pipe_fence
**dst_fence
,
115 struct pipe_fence
*src_fence
);
117 int (*fence_is_signalled
)( struct i915_winsys
*sws
,
118 struct pipe_fence
*fence
);
120 int (*fence_wait
)( struct i915_winsys
*sws
,
121 struct pipe_fence
*fence
);
125 #define I915_BUFFER_ACCESS_WRITE 0x1
126 #define I915_BUFFER_ACCESS_READ 0x2
128 #define I915_BUFFER_USAGE_LIT_VERTEX (PIPE_BUFFER_USAGE_CUSTOM << 0)
131 struct pipe_context
*i915_create( struct pipe_winsys
*,
132 struct i915_winsys
*,