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
34 * This isn't currently true as the winsys needs i915_batchbuffer.h
41 #include "pipe/p_defines.h"
49 /* Pipe drivers are independent of both GL and the window system.
50 * The window system provides a buffer manager and a set of additional
51 * hooks for things like command buffer submission, etc.
53 * There clearly has to be some agreement between the window system
54 * driver and the hardware driver about the format of command buffers,
58 struct i915_batchbuffer
;
61 struct pipe_fence_handle
;
67 * Additional winsys interface for i915simple.
69 * It is an over-simple batchbuffer mechanism. Will want to improve the
70 * performance of this, perhaps based on the cmdstream stuff. It
71 * would be pretty impossible to implement swz on top of this
74 * Will also need additions/changes to implement static/dynamic
79 void (*destroy
)( struct i915_winsys
*sws
);
82 * Get the current batch buffer from the winsys.
84 struct i915_batchbuffer
*(*batch_get
)( 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
*buf
,
98 unsigned access_flags
,
104 void (*batch_flush
)( struct i915_winsys
*sws
,
105 struct pipe_fence_handle
**fence
);
108 #define I915_BUFFER_ACCESS_WRITE 0x1
109 #define I915_BUFFER_ACCESS_READ 0x2
111 #define I915_BUFFER_USAGE_LIT_VERTEX (PIPE_BUFFER_USAGE_CUSTOM << 0)
112 #define I915_BUFFER_USAGE_SCANOUT (PIPE_BUFFER_USAGE_CUSTOM << 1)
116 * Create i915 pipe_screen.
118 struct pipe_screen
*i915_create_screen( struct pipe_winsys
*winsys
,
122 * Create a i915 pipe_context.
124 struct pipe_context
*i915_create_context( struct pipe_screen
*screen
,
125 struct pipe_winsys
*winsys
,
126 struct i915_winsys
*i915
);
129 * Used for the winsys to get the buffer used for a texture
130 * and also the stride used for the texture.
132 * Buffer is referenced for you so you need to unref after use.
134 * This is needed for example kms.
136 boolean
i915_get_texture_buffer( struct pipe_texture
*texture
,
137 struct pipe_buffer
**buf
,