History log of /external/mesa3d/src/mesa/drivers/dri/i965/intel_buffers.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c738ea1191cd1b5a0dc60b0e6d05fd918083e961 18-Jul-2012 Paul Berry <stereotype441@gmail.com> intel: Make more consistent use of _mesa_is_{user,winsys}_fbo()

A lot of code was still differentiating between between winsys and
user fbos by testing the fbo's name against zero. This converts
everything in the i915 and 965 drivers over to use _mesa_is_user_fbo()
and _mesa_is_winsys_fbo().

Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
4433b0302d0aa9dc61002e8bb4fd1b752b0be338 20-Apr-2012 Brian Paul <brianp@vmware.com> intel: use _mesa_is_winsys/user_fbo() helpers

Reviewed-by: Eric Anholt <eric@anholt.net>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
c979fe3e200f42ff1fad75ebdbebe69da27e1aaa 06-Jan-2012 Anuj Phogat <anuj.phogat@gmail.com> Enable is_front_buffer_rendering variable in case of GL_FRONT_AND_BACK

glDrawBuffer(GL_FRONT_AND_BACK) results in to segmentation fault if
intel->is_front_buffer_rendering is not enabled with GL_FRONT_AND_BACK.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44153

Reported-by: Yi Sun <yi.sun@intel.com>
Signed-off-by: Anuj Phogat <anuj.phogat@gmail.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
da2816a45e6e3a33246a341fee72e6f893f315d9 16-Nov-2011 Chad Versace <chad.versace@linux.intel.com> intel: Replace intel_renderbuffer::region with a miptree [v3]

Essentially, this patch just globally substitutes `irb->region` with
`irb->mt->region` and then does some minor cleanups to avoid segfaults
and other problems.

This is in preparation for
1. Fixing scatter/gather for mipmapped separate stencil textures.
2. Supporting HiZ for mipmapped depth textures.

As a nice benefit, this lays down some preliminary groundwork for easily
texturing from any renderbuffer, even those of the window system.

A future commit will replace intel_mipmap_tree::hiz_region with a miptree.

v2:
- Return early in intel_process_dri2_buffer_*() if region allocation
fails.
- Fix double semicolon.
- Fix miptree reference leaks in the following functions:
intel_process_dri2_buffer_with_separate_stencil()
intel_image_target_renderbuffer_storage()

v3:
- [anholt] Fix check for hiz allocation failure. Replace
``if (!irb->mt)` with ``if(!irb->mt->hiz_region)``.

Reviewed-by: Eric Anholt <eric@anholt.net>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Signed-off-by: Chad Versace <chad.versace@linux.intel.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
2e5a1a254ed81b1d3efa6064f48183eefac784d0 07-Oct-2011 Kenneth Graunke <kenneth@whitecape.org> intel: Convert from GLboolean to 'bool' from stdbool.h.

I initially produced the patch using this bash command:
for file in {intel,i915,i965}/*.{c,cpp,h}; do [ ! -h $file ] && sed -i
's/GLboolean/bool/g' $file && sed -i 's/GL_TRUE/true/g' $file && sed -i
's/GL_FALSE/false/g' $file; done

Then I manually added #include <stdbool.h> to fix compilation errors,
and converted a few functions back to GLboolean that were used in core
Mesa's function pointer table to avoid "incompatible pointer" warnings.

Finally, I cleaned up some whitespace issues introduced by the change.

Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Acked-by: Chad Versace <chad@chad-versace.us>
Acked-by: Paul Berry <stereotype441@gmail.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
17fa6772d7e223f940dd8ec4e4f6cf8cab9a03c7 26-Aug-2011 Ian Romanick <ian.d.romanick@intel.com> intel: Silence "warning: unused parameter ‘fb’"

The gl_framebuffer was not used in intel_draw_buffer, so remove it.

Reviewed-by: Eric Anholt <eric@anholt.net>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f34ec6169dc8b96e3958a42b51c9048c5f42ed80 12-Jul-2011 Eric Anholt <eric@anholt.net> intel: Move intel_draw_buffers() code into each driver.

The illusion of shared code here wasn't fooling anybody. It was
tempting to keep i830 and i915 still shared, but I think I actually
want to make them diverge shortly.

Reviewed-by: Chad Versace <chad@chad-versace.us>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
6062692cc6cd2a88d854b304d9a85bcf4bab0d11 23-Jun-2011 Chad Versace <chad@chad-versace.us> intel: Fix workaround for _mesa_update_framebuffer

In intel_draw_buffer, there exists a workaround to prevent
_mesa_update_framebuffer from creating a swrast depth wrapper when
using separate stencil. This commit fixes the workaround, which was
incomplete for s8z24 texture renderbuffers.

Fixes fbo-blit-d24s8 on gen5 with separate stencil manually enabled.

Signed-off-by: Chad Versace <chad@chad-versace.us>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
39d0e3632a4ccb10f2ce6578151e854ba52d3c0e 16-Jun-2011 Chad Versace <chad@chad-versace.us> intel: Add fields to intel_renderbuffer for unwrapping packed depth/stencil buffers

Add the following fields:
intel_renderbuffer.wrapped_depth;
intel_renderbuffer.wrapped_stencil

If the intel_context is using separate stencil and the renderbuffer has
a packed depth/stencil format, then wrapped_depth and wrapped_stencil are
the real renderbuffers.

Alter the following functions to accomodate the wrapped buffers:
intel_delete_renderbuffer
intel_draw_buffer
intel_get_renderbuffer
intel_renderbuffer_map
intel_renderbuffer_unmap

Subsequent commits allocate renderbuffer storage for wrapped_depth and
wrapped_stencil.

Reviewed-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Chad Versace <chad@chad-versace.us>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
c095335fa54498ec54e4587b5f84ad6afd8f1857 25-May-2011 Eric Anholt <eric@anholt.net> intel: Drop doubly irrelevant code in intelReadBuffers.

First, FBO read/draw == NULL validation happens in mesa core not
intelReadBuffers -> intel_draw_buffers. Second, that condition is no
longer tested for in our driver since ARB_ES2_compatibility was added.

Reviewed-by: Brian Paul <brianp@vmware.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
ce8fdf666fc14aa5b9672be1711dfc1c0039efd0 23-May-2011 Chad Versace <chad@chad-versace.us> intel: Fix intel_draw_buffer() to accomodate hiz and separate stencil

The logic of intel_draw_buffers() expected that stencil buffers were
always combined depth/stencil.

Reviewed-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Chad Versace <chad@chad-versace.us>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f9995b30756140724f41daf963fa06167912be7f 12-Oct-2010 Kristian Høgsberg <krh@bitplanet.net> Drop GLcontext typedef and use struct gl_context instead
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
bcf63dbbd8fd31b724294b34a62a0e6c565dce87 08-Jun-2010 Eric Anholt <eric@anholt.net> intel: Flag NEW_BUFFERS when changing draw buffers.

There were entries to this function (most imporantly, prepare_render
-> update_renderbuffers) that wouldn't have had NEW_BUFFERS set, but
brw_wm_surface_state (the i965 state tracking the drawing regions)
expected this to change.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
3d99e990c078f3e1096e7d09bc686643e71d5681 24-Mar-2010 Eric Anholt <eric@anholt.net> i965: Stop abusing ctx->NewState flags for storing driver internal changes.

We're still abusing the flags by putting them where our driver stores
ctx->NewState changes. Making them into more restricted state change
flags would be a project for later.

Fixes a failure where calling intel_draw_buffer() too often would trip
up Mesa assertions about when Mesa state could get changed, when it hadn't.

Bug #27034.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
d449627829e1a4a3250a1a723af2f4e3cd5fd194 18-Feb-2010 Kristian Høgsberg <krh@bitplanet.net> intel: Implement the DRI2 invalidate function properly

This uses a stamp mechanisms to mark the DRI drawable as invalid.
Instead of immediately updating the buffers we just bump the drawable
stamp and call out to DRI2GetBuffers "later".

"Later" used to be at LOCK_HARDWARE time, and this patch brings back
callouts at the points where we used to call LOCK_HARDWARE. A new function,
intel_prepare_render(), is called where we used to call LOCK_HARDWARE,
and if the buffers are invalid, we call out to DRI2GetBuffers there.

This lets us invalidate buffers only when notified instead of on
every glViewport() call. If the loader calls the DRI invalidate
entrypoint, we disable viewport triggered buffer invalidation.

Additionally, we can clean up the old viewport mechanism a bit,
since we can just invalidate the buffers and not worry about
reentrancy and whatnot.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
c6e26d76c7f59b51be00c960112c85ad4b3d2334 31-Jan-2010 Vinson Lee <vlee@vmware.com> intel: Remove unnecessary headers.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
c8e6a0f2f8637d803006d207bb2fb8e4292bdb28 27-Jan-2010 Eric Anholt <eric@anholt.net> intel: Use a handy helper in glReadPixels source clipping.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
a389d6bd566ba241a285c3a33039d5e964bc8f30 27-Jan-2010 Eric Anholt <eric@anholt.net> intel: Remove the remaining cliprects code from DRI1.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
9b22427911ad27efc1f36faee9462c6082d0417c 25-Jan-2010 Brian Paul <brianp@vmware.com> Merge branch 'mesa_7_7_branch'

Conflicts:

src/mesa/drivers/dri/intel/intel_screen.c
src/mesa/drivers/dri/intel/intel_swapbuffers.c
src/mesa/drivers/dri/r300/r300_emit.c
src/mesa/drivers/dri/r300/r300_ioctl.c
src/mesa/drivers/dri/r300/r300_tex.c
src/mesa/drivers/dri/r300/r300_texstate.c
fb6bff3712d71cfe131fbf70154d326cdf39e7c8 23-Jan-2010 Vinson Lee <vlee@vmware.com> intel: Remove unnecessary headers.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
2861d9200be15cc44e8825387d3bd79086523c67 02-Jan-2010 Kristian Høgsberg <krh@bitplanet.net> intel: Drop more cliprect bookkeeping
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
d61f07318c8678901b948fdaa8ccdf37aa3203e9 01-Jan-2010 Kristian Høgsberg <krh@bitplanet.net> Remove leftover __DRI{screen,drawable,context}Private references

As part of the DRI driver interface rewrite I merged __DRIscreenPrivate
and __DRIscreen, and likewise for __DRIdrawablePrivate and
__DRIcontextPrivate. I left typedefs in place though, to avoid renaming
all the *Private use internal to the driver. That was probably a
mistake, and it turns out a one-line find+sed combo can do the mass
rename. Better late than never.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
089144e4e525883995d609af5040b2355043945e 29-Dec-2009 Eric Anholt <eric@anholt.net> intel: Allow binding a stencil but not a depth buffer.

Wine's d3d9 visual.c testcase tries this a lot, so I've added some
piglit tests (fbo-nodepth-test, fbo-nostencil-test, fbo-stencil-only)
and enabled it.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
11522b74b318db9d099466ff226124c23595e8e2 15-Dec-2009 Ian Romanick <ian.d.romanick@intel.com> Merge branch 'mesa_7_6_branch' into mesa_7_7_branch

Conflicts:
src/gallium/drivers/softpipe/sp_quad_blend.c
f23d01e726a57cd6b8e31f1049ee5853773df7ea 15-Dec-2009 Ian Romanick <ian.d.romanick@intel.com> intel: Fallback to software if drawable size is > MaxRenderbufferSize

This prevents the mystery blank window if, for example, glxgears is
resized larger than 2048 wide on 915. Since the Intel drivers in Mesa
7.6 lack GTT mapped fallbacks, the performance is a slideshow at
best. On Mesa 7.7 and later the performance is much better.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
bcbfda71b03303d3f008a6f3cf8cb7d9667bf8d2 02-Nov-2009 Brian Paul <brianp@vmware.com> intel: avoid unnecessary front buffer flushing/updating

Before, if we just called glXMakeCurrent() and didn't render anything we'd
still trigger a flushFrontBuffer() call.

Now only set the intel->front_buffer_dirty field at state validation time
just before we draw something.

NOTE: additional calls to intel_check_front_buffer_rendering() might be
needed if I missed some rendering paths.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
1f196b786d6bd0c6a5dbdc638574ff716cc3d4de 29-Oct-2009 Brian Paul <brianp@vmware.com> Merge branch 'texformat-rework'

Conflicts:
src/mesa/drivers/dri/radeon/radeon_fbo.c
src/mesa/drivers/dri/s3v/s3v_tex.c
src/mesa/drivers/dri/s3v/s3v_xmesa.c
src/mesa/drivers/dri/trident/trident_context.c
src/mesa/main/debug.c
src/mesa/main/mipmap.c
src/mesa/main/texformat.c
src/mesa/main/texgetimage.c
33531614de94d396d10a3bed4a020abe2e2a40b5 27-Oct-2009 Brian Paul <brianp@vmware.com> intel: fix comment, formatting
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
68d94a608a6d46156a567b8f0e011ac58054975e 22-Oct-2009 Brian Paul <brianp@vmware.com> intel: use MESA_FORMAT_S8_Z24 format and avoid z24s8/s8z24 conversions
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
45e76d2665b38ba3787548310efc59e969124c01 09-Oct-2009 Brian Paul <brianp@vmware.com> mesa: remove a bunch of gl_renderbuffer fields

_ActualFormat is replaced by Format (MESA_FORMAT_x).
ColorEncoding, ComponentType, RedBits, GreenBits, BlueBits, etc. are
all replaced by MESA_FORMAT_x queries.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
df70d3049a396af3601d2a1747770635a74120bb 20-Jun-2009 Eric Anholt <eric@anholt.net> intel: Also get the DRI2 front buffer when doing front buffer reading.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
4c6f82989983eecc0b3b724716cb3bcb675664c5 15-May-2009 Eric Anholt <eric@anholt.net> i915: Use Stencil.Enabled instead of Stencil._Enabled in DrawBuffers.

The _Enabled field isn't updated at the point that DrawBuffers is called,
and the Driver.Enable() function does the testing for stencil buffer
presence anyway.

bug #21608 for Radeon
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
62043b27575c378c027251316421e4699f461108 02-May-2009 Brian Paul <brianp@vmware.com> mesa: in glReadBufer() set _NEW_BUFFERS, not _NEW_PIXEL

Since GL_READ_BUFFER is historically part of the gl_pixel_attrib group
it made sense to signal changes with _NEW_PIXEL. But now with FBOs it's
also part of the framebuffer state.

Now _NEW_PIXEL strictly indicates pixels transfer state changes.

This change avoids framebuffer state validation when any random bit of
pixel-transfer state is set.

DRI drivers updated too: don't check _NEW_COLOR when updating framebuffer
state. I think that was just copied from the Xlib driver because we care
about dither enable/disable state there.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
2085cf24628be7cd297ab0f9ef5ce02bd5a006e2 28-Apr-2009 Ian Romanick <ian.d.romanick@intel.com> Test either GL_FRONT_LEFT or GL_FRONT for front-buffer rendering

For non-stereo visuals, which is all we support, we treat
GL_FRONT_LEFT as GL_FRONT. However, they are technically different,
and they have different enum values. Test for either one to determine
if we're in front-buffer rendering mode.

This fix was suggested by Pierre Willenbrock.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f2272b5b2fd9195fe8f9eccfdd2e3c13d18a35e7 21-Apr-2009 Ian Romanick <idr@freedesktop.org> intel / DRI2: When available, use DRI2GetBuffersWithFormat

This interface gives the driver two important features. First, it can
allocate the (fake) front-buffer only when needed. Second, it can
tell the buffer allocator the format of buffers being allocated. This
enables support for back-buffer and depth-buffer with different bits
per pixel.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Kristian Høgsberg <krh@redhat.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
153012b29b4f2183a1be6a01eec63e720a192718 11-Apr-2009 Ian Romanick <ian.d.romanick@intel.com> DRI2: Don't fault on NULL DrawBuffer

It is possible for ctx->DrawBuffer to be NULL, so don't fault when
that happens. This change is not being committed to master because it
doesn't appear to be necessary there.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>

Cherry picked from mesa_7_4_branch, commit 49e0c74ddd91900fc4effb6d305d56e0563b456d
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
43cf0d1eebb9f425e1a0e176394b64e2cb406709 06-Apr-2009 Ian Romanick <idr@freedesktop.org> intel / DRI2: Track and flush front-buffer rendering

Track two flags: whether or not front-buffer rendering is currently
enabled and whether or not front-buffer rendering has been enabled
since the last glFlush. If the second flag is set, the front-buffer
is flushed via a loader call back. If the first flag is cleared, the
second flag is cleared at this time.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Kristian Høgsberg <krh@redhat.com>
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
98826950529041a022f736d183b52421eedead31 05-Mar-2009 Eric Anholt <eric@anholt.net> i965: Add a note about why the _NEW_STENCIL is required in draw_buffers.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
91e61f435a71436c209934a0ece165b540aba3e0 02-Mar-2009 Brian Paul <brianp@vmware.com> mesa: use Stencil._Enabled field instead of Stencil.Enabled
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
ac0dfbdf0f5e5dea08ec717ae8c4e1e141b15c05 30-Jan-2009 Eric Anholt <eric@anholt.net> i915: Only call CalcViewport from DrawBuffers instead of Viewport.

This saves an inadvertent round-trip to the X Server on DrawBuffers, which was
hurting some metaops.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
4451eb2e7533a41f67ed21d05a8d9ab5efec77e9 26-Jan-2009 Brian Paul <brianp@vmware.com> intel: move glClear-related code into new intel_clear.c file
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
6fcebbe719eab1f8e292c8dcd6c3e898b0f8d261 26-Jan-2009 Brian Paul <brianp@vmware.com> intel: Move swap-related functions from intel_buffers.c to new intel_swapbuffers.c
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
e57e39896049a045751201e912779872026fc741 23-Jan-2009 Jesse Barnes <jbarnes@virtuousgeek.org> intel: fix the mismerge of the vblank pipe enable sanity check

Fix the last merge fix, had the blocks ordered incorrectly.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
216bff5fd4699a694a1d76f91c4ee193c2bbe23a 23-Jan-2009 Jesse Barnes <jbarnes@virtuousgeek.org> intel: move pipe enable sanity check to where it belongs

Bah, applied the patches in the wrong order, not Owain's fault...
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
0b5266ff648b03b3f2beda9838598abc00c4f7b2 21-Jan-2009 Owain Ainsworth <zerooa@googlemail.com> intel: fix vblank crtc selection with DRI1 when only one pipe is enabled.

On Mobile chipsets, we often enable PipeB instead of PipeA, but the test
in here was insufficient, falling back to pipe A if the area
intersection returned zero. Therefore, in the case where a window went
off to the top of the left of the screen, it would freeze, waiting on
the wrong vblank.

Fix this mess by checking the sarea for a crtc being zero sized, and in
that case always default to the other one.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
39b4061bb9be540dfb51891e22c505bc235ec8a2 21-Jan-2009 Owain G. Ainsworth <oga@openbsd.org> intel: Prevent an "irq is not working" printf when only pipe B is enabled.

intelMakeCurrent is called before intelWindowMoved (in fact, it calls
it), so calculation of the correct vblank crtc has not happened yet.
Fix this by making a function that fixes up a set of vblank flags and
call if from both functions.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f8a7e497acf17cfdefe401815c7063aaf39d4200 22-Jan-2009 Brian Paul <brianp@vmware.com> intel: remove/disable the "paired depth/stencil" code

We only allow combined depth+stencil renderbuffers so the complicated code
for splitting and combining separate depth and stencil buffers is no longer
needed.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
b27057b381fd8e478f4a31cf790f30a4bf1538cf 22-Jan-2009 Brian Paul <brianp@vmware.com> intel: asst clean-ups, simplifications in intel_draw_buffer()
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
d1eca7f558fa3a20cfe1fe78125d8b7f7751def6 22-Jan-2009 Brian Paul <brianp@vmware.com> i965: minor reformatting
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
39e6d0d8108fe6d222865e7bb9de1e3cea18b4c4 20-Jan-2009 Timo Aaltonen <tjaalton@cc.hut.fi> [intel] Go back to using the typedef for the sarea struct

The upstream linux kernel headers and libdrm kernel headers disagree on the
tag name for the sarea struct: _drm_i915_sarea vs drm_i915_sarea. They
both typedef it to drm_i915_sarea_t though, so just use that.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
b5da7feee03abd7ca52312476bd75d28d1afddf4 14-Jan-2009 Owain G. Ainsworth <oga@openbsd.org> Remove intel pageflipping support in its entirety.

It's been broken and deprecated for a while, so it's time to die. This has the
wonderful benefit of cleaning up the code a fair amount; making it marginally
less twisty.

I'm unsure if the for loops in IntelWindowMoved are still needed.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
b359350017a8f0328912f19d233bcdcc256aded1 20-Dec-2008 Dave Airlie <airlied@redhat.com> Remove third buffer support from Mesa.

This is part of the deprecated pageflipping infrastructure.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
0cade4de4f74f6b0e86fb6622e2fc370c73fd840 20-Oct-2008 Eric Anholt <eric@anholt.net> intel: Don't keep intel->pClipRects, and instead just calculate it when needed.

This avoids issues with dereferencing stale cliprects around intel_draw_buffer
time. Additionally, take advantage of cliprects staying constant for FBOs and
DRI2, and emit cliprects in the batchbuffer instead of having to flush batch
each time they change.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
fc19536aa989ad61e95c281883d32860d767f8ef 04-Oct-2008 Eric Anholt <eric@anholt.net> intel: Push flushing for cliprects changes down into the cliprects changes.

This lets us short-circuit when we're leaving the same cliprects in place,
which becomes quite common with metaops clears, and may be useful for some of
our FBO paths.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
ecadb51bbcb972a79f3ed79e65a7986b9396e757 18-Sep-2008 Brian Paul <brian.paul@tungstengraphics.com> mesa: added "main/" prefix to includes, remove some -I paths from Makefile.template
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f56b569e9af356c11869ee49a4669bb01b75397e 13-Aug-2008 Kristian Høgsberg <krh@redhat.com> DRI2: Drop sarea, implement swap buffers in the X server.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f75843a517bd188639e6866db2a7b04de3524e16 24-Aug-2008 Dave Airlie <airlied@linux.ie> Revert "Revert "Merge branch 'drm-gem'""

This reverts commit 7c81124d7c4a4d1da9f48cbf7e82ab1a3a970a7a.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
7c81124d7c4a4d1da9f48cbf7e82ab1a3a970a7a 24-Aug-2008 Dave Airlie <airlied@linux.ie> Revert "Merge branch 'drm-gem'"

This reverts commit 53675e5c05c0598b7ea206d5c27dbcae786a2c03.

Conflicts:

src/mesa/drivers/dri/i965/brw_wm_surface_state.c
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
1e645b365900cf1c71ca5594bd6b549a1f203040 26-Jul-2008 Ian Romanick <ian.d.romanick@intel.com> Merge branch 'master' into drm-gem

Conflicts:

src/mesa/drivers/dri/common/dri_bufmgr.c
src/mesa/drivers/dri/i965/brw_wm_surface_state.c
9a4be9785f932bedf727fbf88244ac1b158b09a5 24-Jul-2008 Jesse Barnes <jbarnes@jbarnes-t61.(none)> intel: remove buffer swap debug output

Accidentally pushed as part of the last commit.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
97988ccc46c0248177cd71937021ca8cc2a7452b 22-Jul-2008 Jesse Barnes <jbarnes@jbarnes-t61.(none)> intel: fix buffer swaps and enable page flipping on 965

Some buffer swap intel render buffer fields (pf_num_pages & vbl_pending) are
also used for page flipping, so enable the code that sets & updates them on
965. This allows buffer swaps and page flips to work on 965 and prevents hangs
in LOCK_HARDWARE in the buffer swap case due to an uninitialized vbl_pending
field.

Fixes FDO #16118.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
f5d03af109e0c6fdd7cc6786f8ae40f8ae626f5a 06-Jun-2008 Keith Packard <keithp@keithp.com> [intel-gem] Call the new throttle ioctl from swap buffers

Swap buffers is a fairly reasonable time to wait for the hardware for a
while; this keeps us from overrunning the ring.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
fcb7cb9e72ecac7c165a3a6ed7a033e2e6793a26 13-Mar-2008 Zou Nan hai <nanhai.zou@intel.com> [i965] multiple rendering target support
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
6cb3f5c4d8618a14bb7ad1d9df10ed7e648a7b2b 28-Feb-2008 Kristian Høgsberg <krh@redhat.com> Use __DRIextension mechanism providing loader functionality to the driver.

Instead of passing in a fixed struct, the loader now passes in a list
of __DRIextension structs, to advertise the functionality it can provide
to the driver. Each extension is individually versioned and can be
extended or phased out as the interface develops.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
1c718c0d78cf4eae9e02b03a0abbec384db948a6 22-Feb-2008 Alan Hourihane <alanh@tungstengraphics.com> Use drm_i915_sarea instead of drmI830Sarea and remove i830_common.h
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
c5c73c1b605611faf0f06df9b5d08d8984388238 21-Jan-2008 Kristian Høgsberg <krh@temari.boston.redhat.com> Hook up i915 driver to new DRI2 infrastructure.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
9bf91229257c8b26710a23795ae1094aa98db8a8 10-Jan-2008 Eric Anholt <eric@anholt.net> [intel] Remove gratuitous (batchbuffer) flush before doing buffer clears.

Increases OA performance by about 3%.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
4e5b3626a1fc42ff7a88264ded8f0997b0fcd22e 10-Jan-2008 Eric Anholt <eric@anholt.net> [intel] Remove a gratuitous flush at the end of ClearWithTris.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
ab2933df65628d8f1f0a3f49129442bc8d2c3a2b 10-Jan-2008 Eric Anholt <eric@anholt.net> [intel] Only flush batch when changing draw buffers, not every cliprect update.

The previous code would reference freed memory on window moves.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
a04b632350e5d0e9994fc667afc59407a39da0ba 10-Jan-2008 Eric Anholt <eric@anholt.net> [intel] Add more cliprect modes to cover other meanings for batch emits.

The previous change gave us only two modes, one which looped over the batch
per cliprect (3d drawing) and one that didn't (state updeast).
However, we really want 4:

- Batch doesn't care about cliprects (state updates)
- Batch needs DRAWING_RECTANGLE looping per cliprect (3d drawing)
- Batch needs to be executed just once (region fills, copies, etc.)
- Batch already includes cliprect handling, and must be flushed by unlock time
(copybuffers, clears).

All callers should now be fixed to use one of these states for any batchbuffer
emits. Thanks to Keith Whitwell for pointing out the failure.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
beddf653a914903156712aa472b5deaddb7bbaed 09-Jan-2008 Eric Anholt <eric@anholt.net> [intel] Clean up cliprect handling in intel drivers.

In particular, batch buffers are no longer flushed when switching from
CLIPRECTS to NO_CLIPRECTS or vice versa, and 965 just uses DRM cliprect
handling for primitives instead of trying to sneak in its own to avoid the
DRM stuff. The disadvantage is that we will re-execute state updates per
cliprect, but the advantage is that we will be able to accumulate larger
batch buffers, which were proving to be a major overhead.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
601a6b872c33bfe3cb4ea03a5a8ba5ebe92dedaf 07-Jan-2008 Brian <brian.paul@tungstengraphics.com> Replace gl_framebuffer's _ColorDrawBufferMask with _ColorDrawBufferIndexes

Each array element is now a BUFFER_x token rather than a BUFFER_BIT_x bitmask.
The number of active color buffers is specified by _NumColorDrawBuffers.
This builds on the previous DrawBuffer changes and will help with drivers
implementing GL_ARB_draw_buffers.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
ff73c783cc47361ff0dd819c82d067b4b85870dd 06-Jan-2008 Brian <brian.paul@tungstengraphics.com> Simplify ctx->_NumColorDrawBuffers, _ColorDrawBuffers and fix bug 13835.

These fields are no longer indexed by shader output. Now, we just have
a simple array of renderbuffer pointers.

If the shader writes to gl_FragData[i], send those colors to the N
_ColorDrawBuffers. Otherwise, replicate the single gl_FragColor (or
the fixed-function color) to the N _ColorDrawBuffers.

A few more changes and simplifications can follow from this...
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
bea6b5fe5aa3138cec8d057766ae48da4aa57dee 20-Dec-2007 Eric Anholt <eric@anholt.net> [965] Enable EXT_framebuffer_object.

To do so, merge the remainnig necessary code from the buffers, blit, span, and
screen code to shared, and replace it with those.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
b2f62609d02b91cc42c786200fa0c123e1fd2dcb 20-Dec-2007 Eric Anholt <eric@anholt.net> [intel] Allow driver hooks to be NULL in intel_buffers.c and just update flags.

The 965 driver relies on flag checking instead of these hooks, and will be
using this code soon.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
fcd1e9dad6949e02380593a166432dbac311c80e 20-Dec-2007 Eric Anholt <eric@anholt.net> [i915] Move meta_draw_quad into the vtbl with other meta operations.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
d2d82f8a29d3698313956739a7d20704a62c6925 19-Dec-2007 Eric Anholt <eric@anholt.net> [915] Set cliprects in the drawbuffer software fallback case as well.

Otherwise, we may violate cliprect asssertions on clearing the buffers, which
isn't affected by the fallback.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
0dc2c68ffc379aa04247eb48b84b2fac69949bbd 18-Dec-2007 Eric Anholt <eric@anholt.net> [915] Fix clear color when clearing with triangles.

The diffuse color format is always ARGB32, regardless of the destination
surface format.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
6f1bfdc4bf5b72ac705b8cbb2dc431e133dcb5b8 18-Dec-2007 Eric Anholt <eric@anholt.net> [i915] Remove redundant set_draw_region code (like the comment says).
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
33487c15ba8324bf0b635293214cad246661915e 18-Dec-2007 Eric Anholt <eric@anholt.net> [intel] Improve INTEL_DEBUG=blit description of clearing.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
1e0413230648f5ed18bfbdfcb87bf63473ed91b2 17-Dec-2007 Michel Dänzer <michel@tungstengraphics.com> i915: Fix issues with glDrawBuffer(GL_NONE).

Don't dereference NULL renderbuffer pointer, and make sure the software
fallback sticks.

Fixes https://bugs.freedesktop.org/show_bug.cgi?id=13694 .
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
df3c530bedd0ee59e0ae5c18a916f78fd3f7559a 10-Nov-2007 Eric Anholt <eric@anholt.net> [i915] Push locking in intelClearWithTris down inside meta_draw_poly.

The lock coverage and checks for cliprects were unneeded since the batchbuffer
will have INTEL_BATCH_CLIPRECTS anyway. It appeared to be a leftover from
intelClearWithBlit.

This makes the locking requirements of i915 meta_draw_quad match i965
meta_draw_quad.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
9724dc1ac7ddd6f547a8aa6d57fa51ed1040db3a 10-Nov-2007 Eric Anholt <eric@anholt.net> [i915] Remove old frontbuffer rotation hack.

This was replaced in previous releases of xserver/dri/libGL by reporting the
damage to the frontbuffer so that the server and driver could handle it
appropriately.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c
77a5bcaff43df8d54e0e0ef833726e4b41d7eb36 07-Nov-2007 Eric Anholt <eric@anholt.net> [intel] Move over files that will be shared with 965-fbo work.
/external/mesa3d/src/mesa/drivers/dri/intel/intel_buffers.c