[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mesa: Changes to 'debian-unstable'



 ChangeLog                                       |160006 ++++++++++++++++++++++++
 debian/changelog                                |    9 
 debian/rules                                    |    2 
 src/mesa/drivers/dri/i965/brw_clip.c            |    3 
 src/mesa/drivers/dri/intel/intel_pixel_bitmap.c |    6 
 src/mesa/drivers/dri/radeon/radeon_screen.c     |    4 
 6 files changed, 160026 insertions(+), 4 deletions(-)

New commits:
commit 04493de67b44577dd81c6e5c2558f7e46cd5df07
Author: Brice Goglin <bgoglin@debian.org>
Date:   Tue Jul 21 22:22:07 2009 +0200

    Prepare changelog for upload

diff --git a/debian/changelog b/debian/changelog
index 28351a6..b5df900 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,11 @@
-mesa (7.5-2) UNRELEASED; urgency=low
+mesa (7.5-2) unstable; urgency=low
 
   * Pull from upstream mesa_7_5_branch up to commit a6b31415
     + radeon/DRI1: if we have HW stencil, only expose fbconfigs with stencil,
       closes: #537732.
   * Install the upstream changelog.
 
- -- Brice Goglin <bgoglin@debian.org>  Tue, 21 Jul 2009 22:21:13 +0200
+ -- Brice Goglin <bgoglin@debian.org>  Tue, 21 Jul 2009 22:21:50 +0200
 
 mesa (7.5-1) unstable; urgency=low
 

commit e06e2b001fc886584e508be0da06c63dcc7c2853
Author: Brice Goglin <bgoglin@debian.org>
Date:   Tue Jul 21 22:21:47 2009 +0200

    Install the upstream ChangeLog

diff --git a/debian/changelog b/debian/changelog
index ce04cb6..28351a6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,8 +3,9 @@ mesa (7.5-2) UNRELEASED; urgency=low
   * Pull from upstream mesa_7_5_branch up to commit a6b31415
     + radeon/DRI1: if we have HW stencil, only expose fbconfigs with stencil,
       closes: #537732.
+  * Install the upstream changelog.
 
- -- Brice Goglin <bgoglin@debian.org>  Tue, 21 Jul 2009 20:05:53 +0200
+ -- Brice Goglin <bgoglin@debian.org>  Tue, 21 Jul 2009 22:21:13 +0200
 
 mesa (7.5-1) unstable; urgency=low
 

commit d740456ee5fa22f14f22db209e437f0065fb4667
Author: Brice Goglin <bgoglin@debian.org>
Date:   Tue Jul 21 20:42:50 2009 +0200

    Install the upstream ChangeLog

diff --git a/ChangeLog b/ChangeLog
new file mode 100644
index 0000000..0f93384
--- /dev/null
+++ b/ChangeLog
@@ -0,0 +1,160006 @@
+commit a6b314150c141f4c73e408b114181e57237540d9
+Author: Eric Anholt <eric@anholt.net>
+Date:   Thu Jul 2 19:21:22 2009 -0700
+
+    intel: Fall back on glBitmap with fog enabled.
+    
+    We would have to build the program with the appropriate fog mode, and
+    also supply the fog coordinate if appropriate.
+    
+    Bug #19413.
+    (cherry picked from commit 8ae02a3919bf31bd33f86208472e100eedb58497)
+
+commit 1b445f96737cf5a1a28e81ff94a2e07b2cac3a96
+Author: Eric Anholt <eric@anholt.net>
+Date:   Mon Jul 20 17:58:12 2009 -0700
+
+    i965: Don't clip everything if FRONT_AND_BACK culling while culling disabled.
+    
+    Fixes everything-black with meta_clear_tris on quake4-mpdemo and doom3-demo.
+    
+    Bug #18844, 22077.
+    (cherry picked from commit 81d555068408d4343d7627c8bedda5675f09bd21)
+
+commit 5ed440400573631f540701f3efd479d8c1592007
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Mon Jul 20 20:26:28 2009 +0200
+
+    radeon: With DRI1, if we have HW stencil, only expose fbconfigs with stencil.
+    
+    Otherwise simple apps like glxgears pick up a DirectColor visual since the X
+    server mixes the depth 32 visual in with the other GLX visuals, and this seems
+    to result in a (mostly) black screen due to a bad ColorMap for a lot of people.
+    
+    The bad ColorMap may be a bug in the apps, the X server or X driver, and
+    regardless of that I think the X server should ideally make the depth 32 GLX
+    visual separate from the rest again, but in the meantime this makes us cope.
+    
+    (depth_bits is either 16 or 24, never 0)
+
+commit cd10996d4f517c69e306eaf6dfb0654432651b3a
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 14:43:29 2009 -0600
+
+    progs/util: remove extfuncs.h (we use GLEW instead)
+
+commit ee0b1bc7d3fe659e0ed2f34a61b322f2bd2b8843
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 13:23:11 2009 -0600
+
+    progs/glsl: finish conversion to GLEW
+    
+    This is a follow-on to b799af91d5ffbee1481161fec29eb4c92b161272.
+    Remove _func function suffix and unneeded #includes.
+
+commit a77b455af05c9987bd0d94084dadb61fe69b17d0
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 12:40:48 2009 -0600
+
+    mesa: set version to 7.5
+
+commit 71b9e102913753bc5af23c774641d6a6dda184d9
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 12:40:44 2009 -0600
+
+    mesa: set version to 7.5
+
+commit 7fd367467273382aeca5952b12111932766279fb
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 12:40:24 2009 -0600
+
+    docs: set date for 7.5 release
+
+commit 27587f46e5377dcc7718e80b5bcbedb03e6d7ee3
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 09:40:45 2009 -0600
+
+    docs: news entry for 7.5 release
+
+commit 8c6e81f97dba8c4a108f63a2236915443db6c3cd
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 17 09:40:28 2009 -0600
+
+    docs: update links to Gallium wiki page on freedesktop.org
+
+commit 2ba98efdf6653a4cb885d576d2e6f349c69679d4
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 19:34:44 2009 +0100
+
+    python/retrace: Process the call no passed to --to option inclusively.
+
+commit cf7e8fbc2ea2739f1955d83751b631c5444a3c91
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 19:32:40 2009 +0100
+
+    python/retrace: Dump the surface copy contents.
+
+commit 5807ccb41b14890a1cdab4cc06806a9cf6c11ecc
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 19:31:36 2009 +0100
+
+    python/retrace: Flush stdout before calling the pipe driver.
+    
+    So that messages are in sync with stderr.
+
+commit d4e6df9ab6e7b707278e3739abee776418c6f527
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 19:20:25 2009 +0100
+
+    mesa: Fix logbase2.
+    
+    It was providing 1 too many for non power two values.
+
+commit 0c4350790ac0639996cbefcf2556ca5748d39454
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 11:21:12 2009 +0100
+
+    python: Hack to prevent segmentation faults when python exits.
+
+commit 4e1e18a772061fe3573f2ee2bf6afe447ee66fd6
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 11:20:12 2009 +0100
+
+    wgl: Expose pipe_screen/pipe_context via an extension.
+
+commit 3ab3209a1f1af7bfd8e09598fbc3586f35169fb2
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 16 11:19:06 2009 +0100
+
+    python: Obtain pipe_screen/pipe_context from the system's OpenGL driver.
+
+commit 6b7b13b5ebcebdca38264d165a95fd22887b90c7
+Author: Luca Barbieri <luca@luca-barbieri.com>
+Date:   Wed Jul 15 11:34:36 2009 -0600
+
+    softpipe: limit blend results to [0,1]
+
+commit d970313b66b3aab3e3d12c65882febcc7c9091a8
+Author: Brian Paul <brianp@vmware.com>
+Date:   Wed Jul 15 11:12:05 2009 -0600
+
+    Fix state flag dependencies for fixed function fragment program updates.
+    
+    I started looking into why _NEW_ARRAY punishes us, and while annotating
+    dependencies noticed that a bunch of dependencies were missing.
+    
+    (cherry picked from master, commit e5f63c403b767f9974e8eb5d412c012b8a69287f)
+
+commit 0474b5cb2ac4cefa12e7080aba397013325fb9a6
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Wed Jul 15 15:37:27 2009 +0100
+
+    python/retrace: Interpret surface_copy.
+
+commit c68f659be3850c5e099311be7c58f8930954631d
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Wed Jul 15 15:37:04 2009 +0100
+
+    python/samples: Use PIPE_FORMAT_Z16_UNORM instead of PIPE_FORMAT_Z32_UNORM.
+    
+    More common. True fix would be to use whatever the screen supports though.
+
+commit fdeb77899052302053459b8a840a747346e30468
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Wed Jul 15 13:29:58 2009 +0100
+
+    mesa: recognize and eliminate repeated error messages
+
+commit 59de430de70c38a2fbe30208190f725a2901613c
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jul 14 16:28:08 2009 +0100
+
+    mesa: split out errorstring switch from _mesa_error
+    
+    Move a chunk of code out of _mesa_error()
+
+commit df5f7a676182dc9d1d8c9c995a009b49bac971e8
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jul 14 16:25:59 2009 +0100
+
+    mesa: remove dead code in _mesa_error
+    
+    Remove early and unused snprintf and where[] string.
+
+commit 6c9d8a6f24db3c947928d72521d5fd544841366e
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jul 14 16:23:04 2009 +0100
+
+    mesa: don't call getenv every time _mesa_error is called
+    
+    Buggy apps can generate thousands of mesa_error calls.  Don't need
+    to keep calling getenv to retreive the same MESA_DEBUG string each
+    time.
+
+commit 9aca6769dfb934e15e848f938b7fb31345a8b3b2
+Author: Brian Paul <brianp@vmware.com>
+Date:   Tue Jul 14 14:26:42 2009 -0600
+
+    mesa: fix texture border color code for glPopAttrib()
+    
+    The texture object's border color used to be stored as GLchan but it's
+    been GLfloat for a while now.
+
+commit 26e58a42b0faa8f4eb2794a1ddee6b66d0ce0efe
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Sat Jul 4 16:01:45 2009 +0200
+
+    progs/tests: Use compressed texture in mipmap_comp_tests
+
+commit b0a17581e20c6993e1ec3ef85801f351366f949b
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Sat Jul 4 07:40:34 2009 +0200
+
+    progs/tests: Tests more views in mipmap_comp_tests
+
+commit a36b9987cd0e6930e8db91322801854206cc1800
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Sun Jun 14 01:04:00 2009 +0200
+
+    progs/tests: Add yet another mipmap test
+
+commit 6ec955efafda961bc7789c22dbde9d3430fc270f
+Author: Brian Paul <brianp@vmware.com>
+Date:   Tue Jul 14 07:58:22 2009 -0600
+
+    mesa: regenerated enums.c file
+
+commit 7325c1ebc8cf88249d0adeadc0f52600e727c762
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Tue Jul 14 11:09:23 2009 +0100
+
+    scons: Monkey patch os.spawnve on Windows to become thread safe.
+    
+    See also:
+    - http://bugs.python.org/issue6476
+    - http://scons.tigris.org/issues/show_bug.cgi?id=2449
+
+commit 4ed1de8b84b587d2be0c0e4ecb6b5f421195f562
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Tue Jul 7 17:56:12 2009 +0100
+
+    mesa: Report the true face number when flushing.
+
+commit 680f7d09b00fdec0dbe5e357639d6b445bb9266e
+Author: Peteri Andras <whysogreen@gmail.com>
+Date:   Mon Jul 13 08:03:16 2009 -0600
+
+    r128: fix two-sided lighting segfault seen in GLUT's olight demo
+
+commit 022e8e582ee408845bc622d56487b220b27df9a6
+Author: Ian Romanick <ian.d.romanick@intel.com>
+Date:   Sun Jul 12 21:07:38 2009 -0700
+
+    intel: Bump driver data, add RC3 tag
+
+commit 1c1307e7c55844f63f7bd7ac02c64f4b936f3c66
+Author: Zack Rusin <zackr@vmware.com>
+Date:   Sat Jul 11 13:48:41 2009 -0400
+
+    gallium: compare the actual register, not all the inputs
+    
+    otherwise we decrement indexes for all registers
+
+commit cff2126f522bb511216f64427b3060467e266f8a
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 16:26:09 2009 -0600
+
+    tgsi: update some assertions
+
+commit a79586ce180a77beb15f6a9b6a72d490ad6e6afd
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 15:44:48 2009 -0600
+
+    tgsi: tgsi: add semantic_names[] string for TGSI_SEMANTIC_FACE
+    
+    Same story as in the tgsi_dump.c code (see prev commit).
+
+commit f01af4dbd26bec433cde08d011a5101edd7d83be
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 15:41:26 2009 -0600
+
+    tgsi: add semantic_names[] string for TGSI_SEMANTIC_FACE
+    
+    Fixes TGSI dump output when front/back-face register is declared.
+    
+    Also, add some assertions to make sure the semantic/interpolate string
+    arrays have as many elements as there are tokens in the p_shader_tokens.h
+    file.  That should catch problems like this in the future.
+
+commit 762c1d11ffbb5179e44117397559e7cc2dfe9cef
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 13:07:45 2009 -0600
+
+    st/mesa: implement indirect addressing for destination registers
+
+commit baa7ff47d548cdcc1ea68657ee1b0500f78041be
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 13:07:16 2009 -0600
+
+    tgis: implement indirect addressing for destination registers
+    
+    Includes the TGSI interpreter, but not the SSE/PPC/etc code generators.
+
+commit ca1b71b78d9c31e9ea7ceed2542ec67f32e6e5c5
+Author: Brian Paul <brianp@vmware.com>
+Date:   Fri Jul 10 12:55:30 2009 -0600
+
+    vbo: fix vbo/dlist memory leak
+    
+    Based on a patch by kristof.ralovich@gmail.com
+
+commit 6ff1a5385ee2a2f3c612254254bf5c1e4f4e593a
+Author: Brian Paul <brianp@vmware.com>
+Date:   Thu Jul 9 13:59:03 2009 -0600
+
+    demos: set 4th component of texcoord to 1.0
+    
+    Avoid potential randomness in resulting texcoords.
+
+commit cade071d525f71069f635fd0b705e64d897b32c4
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Fri Jul 10 14:49:46 2009 +0200
+
+    Remove stale reference to non-Gallium nouveau driver from configure.ac.
+
+commit fcd3572edf5eed47d87774150c2097e0d6245bd2
+Author: Ian Romanick <ian.d.romanick@intel.com>
+Date:   Mon Jun 22 18:22:51 2009 -0700
+
+    mesa: From float type modifier from values to large for singles
+    
+    The values 2147483648.0 and 4294967294.0 are too larget to be stored in single
+    precision floats.  Forcing these to be singles causes bits to be lost, which
+    results in errors in some pixel transfer tests.
+    
+    This fixes bug #22344.
+    (cherry picked from commit 70e72070fce6aa1e0918dcc62c1949465cee69f7)
+
+commit 78af70be3727945d2d81a07b99d5a794f1114c05
+Author: Brian Paul <brianp@vmware.com>
+Date:   Thu Jul 9 08:04:07 2009 -0600
+
+    docs: document gl_TextureMatrix[i][j] array indexing bug fix
+
+commit c86b0766681f986951e53ea852858eb8d6ce9e32
+Author: Brian Paul <brianp@vmware.com>
+Date:   Thu Jul 9 07:58:50 2009 -0600
+
+    glsl: do const parameter optimization for array element actual parameters
+    
+    When a function parameter is const-qualified we can avoid making a copy
+    of the actual parameter (we basically do a search/replace when inlining).
+    This is now done for array element params too, resulting in better code
+    (fewer MOV instructions).
+    
+    We should allow some other types of function arguments here but let's be
+    conservative for the moment.
+
+commit abdb0fdcc05eb9ec87b3d5a3226c3c190e1fbbcd
+Author: Brian Paul <brianp@vmware.com>
+Date:   Thu Jul 9 07:57:29 2009 -0600
+
+    glsl: fix incorrect indexing for gl_TextureMatrix[i][j]
+    
+    The two indexes were mixed up when accessing a row of a matrix in an array
+    of matrices.
+
+commit 36e906aad6d0520db00cc5112fd015497465bc87
+Author: Brian Paul <brianp@vmware.com>
+Date:   Wed Jul 8 14:14:03 2009 -0600
+
+    docs: document glMaterial/glShadeModel display list optimization
+
+commit 4adc9b4a5be72e34d464ce341b011c42517d969a
+Author: Brian Paul <brianp@vmware.com>
+Date:   Tue May 5 16:21:20 2009 -0600
+
+    mesa: only use fallback texture when using shaders, not fixed-function (take two)
+    
+    The semantics are a little different for shaders vs. fixed-function when
+    trying to use an incomplete texture.  The fallback texture returning
+    (0,0,0,1) should only be used with shaders.  For fixed function, the texture
+    unit is truly disabled/ignored.
+    
+    Fixes glean fbo test regression.
+    (cherry picked from commit 01e16befd4809e3e93ee7855a4a5d7df9fe010d9)
+    (cherry picked from commit 51325f44d1e7e62b47795a79f8038d10dc5bc30b)
+    [anholt: squashed these two together from master, skipping the mess in between]
+
+commit 7b861b9b9efdb3ac0dfc3806afcd494cd0ea006c
+Author: Zack Rusin <zackr@vmware.com>
+Date:   Tue Jul 7 12:48:50 2009 -0700
+
+    gallium: fixup register indexes for fog/frontface/point coord
+
+commit 71633abafc935c25da9731bab48c228ceb9b4097
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Tue Jul 7 14:49:52 2009 +0200
+
+    gallium: Fixes for clobbering stencil values in combined depth/stencil textures.
+    
+    Also fix one case where a 32 bit depth value was incorrectly converted to a
+    combined depth/stencil value.
+
+commit 25b492b976632269dfa3de164545d50a53c090ce
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Tue Jul 7 13:52:35 2009 +0200
+
+    GLX/DRI1: Mark GLX visuals with depth != screen depth non-conformant.
+    
+    Such visuals are subject to automatic compositing in the X server, so DRI1
+    can't render to them properly.
+
+commit 96601ec8e0e35d540c1819a48df7f08ec5874ab7
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Tue Jul 7 12:17:04 2009 +0200
+
+    gallium: Only set FRONT_STATUS_COPY_OF_BACK if there is a back buffer.
+    
+    Fixes potential crash when SwapBuffers is called but there's no back buffer.
+
+commit a4d952358d8fd0f9d135c91c37969acdcf394f0a
+Author: Zack Rusin <zackr@vmware.com>
+Date:   Mon Jul 6 21:33:56 2009 -0400
+
+    gallium: more fog extraction fixes
+    
+    fix the cases when fog coord/front face/point coord are used in the same
+    shader.
+
+commit 7fb4becf986872268af4ba3f62c0a85b41ef7e5d
+Author: Ian Romanick <ian.d.romanick@intel.com>
+Date:   Mon Jul 6 11:36:17 2009 -0700
+
+    demos: Fix vsync checking in glxgears
+    
+    Of course glXGetVideoSyncSGI doesn't return the swap interval.  The feature
+    only exists in the Mesa extension... which is the whole reason I created the
+    Mesa extension!  Note that the Mesa extension allows drivers to default to a
+    swap interval of 0.  If the Mesa extension exists, use its value.  Only
+    consider the SGI extension when the Mesa extension is not available.
+    
+    Fixes bug #22604.
+
+commit 1068c15c61a6c76a2da04ed3ca136f0d49abed1d
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Mon Jul 6 18:23:37 2009 +0100
+
+    wgl: Make the stw_framebuffer destructions threadsafe.
+    
+    Ensure no other thread is accessing a framebuffer when it is being destroyed by
+    acquiring both the global and per-framebuffer mutexes. Normal access only
+    needs the global lock to walk the linked list and acquire the per-framebuffer
+    mutex.
+
+commit 6f4167c8a215b561e5ad6eb58a8d875a5b8d8d6a
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Mon Jul 6 17:40:08 2009 +0100
+
+    wgl: Check for multiple threads before GET_CURRENT_CONTEXT.
+    
+    Fixes wglthreads -- the 2nd thread MakeCurrent call was trying to flush
+    the first thread context while still in use.
+
+commit 5470a67335dfd9afffb92ff6521a77519cda40d8
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Mon Jul 6 17:08:37 2009 +0100
+
+    wgl: Listen to WM_WINDOWPOSCHANGED instead of WM_SIZE messages.
+    
+    According to
+    http://blogs.msdn.com/oldnewthing/archive/2008/01/15/7113860.aspx
+    WM_SIZE is generated from WM_WINDOWPOSCHANGED by DefWindowProc so it
+    can be masked out by the application.
+    
+    Also there were some weird bogus WM_SIZE 0x0 messages when starting
+    sharedtex_mt which we don't get like this.
+
+commit fc6e02ce6210d6615af0058f1b57e7ee37a6527f
+Author: Roland Scheidegger <sroland@vmware.com>
+Date:   Fri Jun 26 20:38:07 2009 +0200
+
+    i965: fix fetching constants from constant buffer in glsl path
+    
+    the driver used to overwrite grf0 then use implicit move by send instruction
+    to move contents of grf0 to mrf1. However, we must not overwrite grf0 since
+    it's still used later for fb write.
+    Instead, do the move directly do mrf1 (we could use implicit move from another
+    grf reg to mrf1 but since we need a mov to encode the data anyway it doesn't
+    seem to make sense).
+    I think the dp_READ/WRITE_16 functions may suffer from the same issue.
+    While here also remove unnecessary msg_reg_nr parameter from the dataport
+    functions since always message register 1 is used.
+
+commit c30f23c1231e8443e0880efa5326ccecf6eec034
+Author: Eric Anholt <eric@anholt.net>
+Date:   Wed May 6 21:44:13 2009 -0700
+
+    i965: Remove bad constant buffer constant-reg-already-loaded optimization.
+    
+    Thanks to branching, the state of c->current_const[i].index at the point
+    of emitting constant loads for this instruction may not match the actual
+    constant currently loaded in the reg at runtime.  Fixes a regression in my
+    GLSL program for idr's class since b58b3a786aa38dcc9d72144c2cc691151e46e3d5.
+
+commit 94e1117c9ba259665cd8e790369dcd4c789a2f93
+Author: Michel Dänzer <daenzer@vmware.com>
+Date:   Fri Jul 3 17:50:15 2009 +0200
+
+    intel: Also update stencil bits in intel_update_wrapper().
+    
+    Fixes assertion failure when binding depth/stencil texture to FBO stencil
+    attachment.
+
+commit f580494bef54bb53a34f2798de15f0227f512b76
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Fri Jul 3 16:40:03 2009 +0100
+
+    progs: revert damage to progs/SConscript from recent compressed texture commit
+
+commit b928d18398330d862ab162f687e224b93932824c
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Fri Jul 3 14:26:26 2009 +0100
+
+    mesa/shaders: fix gl_NormalMatrix state parameters
+    
+    gl_NormalMatrix is the inverse transpose of the modelview matrix, but
+    as every matrix here needs to be transposed, we end up with
+    {MODELVIEW_MATRIX, INVERSE}.
+
+commit aa98575ebb97bc38cf40acd3d78b72ee49f7b86b
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Fri Jul 3 10:37:14 2009 +0100
+
+    st/wgl: don't advertise WGL_EXT_swap_interval string
+    
+    This is a tweak to a previous fix -- it's not necessary to actually
+    advertise this extension to prevent these games from crashing -- they
+    ignore the extension string anyway. It's sufficient to just have
+    GetProcAddress return some dummy function addresses for SwapInterval.
+    
+    Given we don't really implement this funcitonality, this is a better
+    fix.
+
+commit cffe7c8bd0397f8d54e2da16a21c7db4345766b8
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Fri Jul 3 14:21:55 2009 +0100
+
+    wgl: Lookup framebuffers by HWND whenever possible.
+    
+    Some applications create several HDCs for the same window, so spite the WGL
+    API is geared towards HDCs it is not reliable searching by HDC.
+
+commit 2a2236606fd6ae473a2f4db6ef6d3d5030261316
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Thu Jul 2 17:24:25 2009 +0100
+
+    mesa: Assume depth textures have a single level unless told otherwise.
+
+commit 588c8625714c744047dd1d710d87b1dfcec48db7
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Thu Jul 2 14:43:16 2009 +0100
+
+    mesa: s/TRUE/GL_TRUE
+    
+    Fix compile breakage on Linux.
+
+commit 798cd2a98d66a1b841930e121676ae1a8f9fb244
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Thu Jul 2 13:28:20 2009 +0100
+
+    glapi: ensure _mesa_lookup_prim_by_nr() is not clobbered on regeneration
+    
+    Propogate changes to enums.c back up to the python source.
+
+commit 1668a679c4aadb37f5af0d6126c414fb9fbbf748
+Merge: b3e8e1c 1fa4cde
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Thu Jul 2 13:29:46 2009 +0100
+
+    Merge commit 'origin/dlist-statechange-shortcircuit' into mesa_7_5_branch
+    
+    Conflicts:
+    	progs/trivial/Makefile
+    
+    Pull in a minimal version of statechange shortcircuiting in display
+    list compilation.  This affects only glMaterial and glShadeModel state,
+    and includes quite a few tests to exercise various tricky cases.
+    
+    If this goes well, will consider extending to all state in the future.
+
+commit b3e8e1cd4c1584f735e35914861ae2e8ae5b6b2b
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Thu Jul 2 11:28:56 2009 +0100
+
+    mesa: ensure UsesFogFragCoord value is set for non-glsl shaders
+    
+    With recent changes to support frontfacing in glsl, it is necessary
+    to ensure that the UsesFogFragCoord value is accurate in all shaders.
+    We were previously not setting it for fixed-function and ARB_fs shaders.
+
+commit 1fa4cde757cc94c0afa40d855309911247974e98
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 19:52:44 2009 +0100
+
+    mesa/vbo: fix compile and replay of nodes ending in a FALLBACK
+    
+    Where vbo save nodes are terminated with a call to DO_FALLBACK(), as in
+    the case of a recursive CallList which is itself within a Begin/End pair,
+    there two problems:
+    1) The display list node's primitive information was incorrect, stating
+    the cut-off prim had zero vertices
+    2) On replay, we would get confused by a primitive that started in a
+    node, but was terminated by individual opcodes.
+    
+    This change fixes the first problem by correctly terminating the last
+    primitive on fallback, and the second by forcing the display list to
+    use the Loopback path, converting all nodes into immediate-mode rendering.
+    
+    The loopback fix is a performance hit, but avoiding this would require
+    a fairly large rework of this code.
+
+commit 70ae7ba818e9d8a5485653b258e76f06c988654c
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 18:40:20 2009 +0100
+
+    mesa/dlist: fixes and improvements for material caching
+    
+    Only short-circuit material call if *all* statechanges from this call
+    are cached.  Some material calls (eg with FRONT_AND_BACK) change more
+    than one piece of state -- need to check all of them before returning.
+    
+    Also, Material calls are legal inside begin/end pairs, so don't need
+    to be as careful about begin/end state as with regular statechanges
+    (like ShadeModel) when caching.  Take advantage of this and do better
+    caching.
+
+commit c48c01c9e7d6d0a43883b7b3333ad42208ea9d44
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 18:35:17 2009 +0100
+
+    progs/trivial: add dlist-mat-tri.c
+
+commit 1ca836f0de7ac23a3d66e109eeda3c2e29b9b17c
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 18:17:39 2009 +0100
+
+    progs/trivial: add test case for short-circuiting material changes
+    
+    Similar to dlist-tri-flat-tri, but using glMaterial calls, which
+    have the extra property of being legal within Begin/End calls.
+
+commit d6c2347d79c50ac18eab96378d79d989f3ffd0b7
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 17:10:56 2009 +0100
+
+    mesa/dlist: don't cache state which may not be replayed on CallList
+    
+    Statechanges which occur before the first End in a display list may
+    not be replayed when the list is called, in particular if it is called
+    from within a begin/end pair.
+    
+    Recognize vulnerable statechanges and do not use them to fill in the
+    state cache.
+
+commit 09a3a28fc8f1ed931304bf27a56fe72768d7861e
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 17:06:50 2009 +0100
+
+    progs/trivial: add dlist-flat-tri.c
+    
+    State-change functions which precede the first call to glEnd() in
+    a compiled list are vulnerable to not being executed when that list
+    is called.
+    
+    In particular this can happen if a list is invoked from within a
+    begin/end pair, as in this example.
+
+commit 7e91d035b9ef65adda39c8b164afa363477d7893
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 17:04:11 2009 +0100
+
+    mesa/dlist: invalidate cached dlist compile state after CallList
+    
+    When compiling a display list containing a CallList, it is necessary to
+    invalidate any assumption about the GL state after the recursive call
+    completes.
+
+commit 2e570be85211f603b820dd2c5e9aa2f29a51fc66
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 17:02:16 2009 +0100
+
+    progs/trivial: add dlist-recursive-call
+    
+    When one display list calls another display list, it is possible
+    that the calling display list makes state-changes or other actions which
+    invalidate any attempt at caching or state-change elimination in the
+    calling list.
+    
+    This test exercises one such case, where the called list consists of just
+    a single glShadeModel() call.
+
+commit 1730eaa2a2454018b4907df2f2bda3c4455137ca
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 16:57:21 2009 +0100
+
+    dlist-tri-flat-tri: make tri render differently if flatshade not enabled
+    
+    When testing flat-shading, it helps to specify per-vertex colors so
+    that you can distinguish between flat & smooth shading.
+
+commit 4147bb24d49a10498e00039fc1dc9aa5f1316777
+Merge: 53f8dcc 6af783b
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 16:28:37 2009 +0100
+
+    Merge branch 'mesa_7_5_branch' into dlist-statechange-shortcircuit
+    
+    Need this to pick up fixes for per-vertex materials.
+
+commit 6af783bea0e171582f86c8456ca521ac242abc39
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 16:19:23 2009 +0100
+
+    progs/trivial: add test case for lighting plus per-vertex materials
+    
+    Exercise material-within-begin/end case.
+
+commit a9ae89d104161c1052beda7e3dcb21b8b7af5ba3
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Sun May 31 19:07:21 2009 -0700
+
+    progs/isosurf: add materials mode for glVertex + TRISTRIP
+
+commit 6dfb89e4a09a269cbd5c4dc725881fbd42eaa18a
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Sun May 31 19:04:06 2009 -0700
+
+    mesa: remove whitespace
+
+commit cea259f0392766e8a2e4749c6d5277d866abbc3b
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Sun May 31 19:03:46 2009 -0700
+
+    mesa: remove dead constant pointsize code from ffvertex_prog.c
+
+commit 79047cc1ddf0332e5b64c9f05a19885cc36c76ae
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Sun May 31 19:03:02 2009 -0700
+
+    mesa: remove dead vertex fog code from ffvertex_prog.c
+
+commit f6c8ca06f649ae1367f61eca6fb7635862bd5584
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Sun May 31 19:01:55 2009 -0700
+
+    mesa: fix material inputs in ffvertex_prog.c
+    
+    Varying material inputs were not being picked up from the same slots
+    where the VBO code is currently placing them (GENERIC0 and above).
+    Most often they were just being ignored.
+
+commit 4c31632817a0bde28ad6c9ee8032d838ce4b7bfb
+Author: Arthur HUILLET <arthur.huillet@free.fr>
+Date:   Tue Jun 30 12:46:27 2009 +0200
+
+    mesa: fix transform_points_3d_no_rot using undefined values in %xmm0
+    
+    Signed-off-by: Arthur HUILLET <arthur.huillet@free.fr>
+
+commit fa5b0364f90be19bb0e1915f1eea691d06fb8929
+Author: Kristof Ralovich <kristof.ralovich@gmail.com>
+Date:   Tue Jun 30 08:31:18 2009 -0600
+
+    glx: plug a leak
+    
+    Swrast was missing a free for the culmination of driConcatConfigs.
+    
+    Use free(), not _mesa_free() since we shouldn't be calling any Mesa
+    functions from the GLX code.  driConcatConfigs() should probably use
+    regular malloc/free to be consistant but the Mesa functions just wrap
+    the libc functions anyway.
+
+commit 52f895df518608321873f53d6f8549bdbaf0059a
+Author: Brian Paul <brianp@vmware.com>
+Date:   Tue Jun 30 08:27:28 2009 -0600
+
+    glx: fix null pointer dereference segfault (bug 22546)
+
+commit 14a2b5445a653e9a8258873300df8f04ac099e60
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Mon Jun 29 16:07:14 2009 +0100
+
+    progs/util: make sure function pointers are initialized
+    
+    Call Init() from CompileShaderFile, was previously only called for the
+    Text version of this function.
+
+commit 6e09c1fd085361212c5bfccf6b2810f3f8052231
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Tue Jun 30 15:09:34 2009 +0100
+
+    mesa: Set FLUSH_EXPLICIT_BIT flags when calling FlushMappedBufferRange.
+    
+    As prescribed by ARB_map_buffer_range.
+
+commit 18a6f0f1a7fd509cebdc364d67b9476df1d33917
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Tue Jun 30 15:07:54 2009 +0100
+
+    util: Set PIPE_BUFFER_USAGE_FLUSH_EXPLICIT when calling buffer_flush_mapped_range.
+
+commit 4ffe2844a46bcd69c0f2c95f04da97e83899e831
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Tue Jun 30 15:07:10 2009 +0100
+
+    gallium: New PIPE_BUFFER_USAGE_FLUSH_EXPLICIT flag for buffer_flush_mapped_range.
+    
+    When a buffer was mapped for write and no explicit flush range was provided
+    the existing semantics were that the whole buffer would be flushed, mostly
+    for backwards compatability with non map-buffer-range aware code.
+    
+    However if the buffer was mapped/unmapped with nothing really written --
+    something that often happens with the vbo -- we were unnecessarily assuming
+    that the whole buffer was written.
+    
+    The new PIPE_BUFFER_USAGE_FLUSH_EXPLICIT flag (based from ARB_map_buffer_range
+    's GL_MAP_FLUSH_EXPLICIT_BIT flag) allows to clearly distinguish the
+    legacy usage from the nothing written usage.
+
+commit 578230dbbffbf5317d6002d1023dcd62b57186f5
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Tue Jun 30 13:59:45 2009 +0200
+
+    st/gl: Add stubs for CompressedTexSubImage[1D|3D]
+
+commit a4fd94a54a75a3418462c30f1240ab50b5f24090
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Tue Jun 30 07:33:54 2009 +0200
+
+    st/gl: Add support for glCompressedTexSubImage
+
+commit ba7f45ac0ca3debb2a250d5e945a2d70b2b72d08
+Author: Jakob Bornecrantz <jakob@vmware.com>
+Date:   Tue Jun 30 13:34:55 2009 +0200
+
+    progs/tests: Add tests for glCompressedTexSubImage
+
+commit f2de2d5f376a868f68a053257f7d6dfcdee6c8ae
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Wed Jul 1 19:09:44 2009 +0100
+
+    util: Increase OutputDebugStringA to 4k.
+    
+    According to http://unixwiz.net/techtips/outputdebugstring.html that's
+    how big the buffer is.
+    
+    The 512bytes limitation is in kernel mode.
+
+commit e2a8ef4430e153589a9d1a284c8f2005a4a98410
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Wed Jul 1 19:06:54 2009 +0100
+
+    mesa: Unbind depth/stencil surface from pipe_framebuffer when none is attached.
+
+commit 6c913411d39fd68eee1c1eeee7b6e81db9785fd1
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Wed Jul 1 17:34:38 2009 +0100
+
+    st/wgl: dummy implementation of wgl swapinterval extension
+    
+    Required as some applications
+    retrieve and call these functions regardless of the fact that we
+    don't advertise the extension and further more the results of
+    wglGetProcAddress are NULL.
+
+commit 1c04731b8721850b6abb12a43a3eec616b850e86
+Author: Zack Rusin <zack@kde.org>
+Date:   Wed Jul 1 10:42:58 2009 -0400
+
+    gallium: fix the front face semantics
+    
+    mesa allocates both frontface and pointcoord registers within the fog
+    coordinate register, by using swizzling. to make it cleaner and easier
+    for drivers we want each of them in its own register. so when doing
+    compilation from the mesa IR to tgsi allocate new registers for both
+    and add new semantics to the respective declarations.
+
+commit e8c4663c11cfbb80ed23b1581cf1f3ccaef28bce
+Author: José Fonseca <jfonseca@vmware.com>
+Date:   Wed Jul 1 10:03:59 2009 +0100
+
+    wgl: Optimize wglGetProcAddress.
+    
+    Do linear search only if prefix matches.
+
+commit c72261f2a886e1f53025c2cf4b38b33ccfd62857
+Author: Eric Anholt <eric@anholt.net>
+Date:   Mon Jun 29 18:48:27 2009 -0700
+
+    i915: Fix assertion failure on remapping a non-BO-backed VBO.
+    
+    Failure to set the obj->Pointer back to null tripped up the assertion.
+    Bug #22428.
+    (cherry picked from commit 57a06d3a48c9af1067ec05e3ad96c58f4b9b99be)
+
+commit 57955451f80c64f70e369508705ae95a515d18d8
+Author: Jon TURNEY <jon.turney@dronecode.org.uk>
+Date:   Sun Jun 21 11:58:25 2009 +0100
+
+    xdemos: Fix xdemos which default to using display :0.0 to default to $DISPLAY
+    
+    Fix xdemos which default to using display :0.0 to default to $DISPLAY,
+    this is kind of irritating when testing on a display other than :0.0
+    
+    Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
+
+commit e5cb11addad31f698dc8261e7f96d5e3af4a85d6
+Author: Keith Whitwell <keithw@vmware.com>
+Date:   Tue Jun 30 19:52:44 2009 +0100
+
+    mesa/vbo: fix compile and replay of nodes ending in a FALLBACK
+    
+    Where vbo save nodes are terminated with a call to DO_FALLBACK(), as in
+    the case of a recursive CallList which is itself within a Begin/End pair,
+    there two problems:
+    1) The display list node's primitive information was incorrect, stating
+    the cut-off prim had zero vertices
+    2) On replay, we would get confused by a primitive that started in a
+    node, but was terminated by individual opcodes.
+    
+    This change fixes the first problem by correctly terminating the last
+    primitive on fallback, and the second by forcing the display list to


Reply to: