summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove ctx->Point._Size and ctx->Line._Width.Brian2007-07-2119-53/+74
| | | | | | The clamping for these values depends on whether we're drawing AA or non-AA points, lines. Defer clamping until drawing time. Drivers could compute and keep clamped AA and clamped non-AA values if desired.
* remove VC6/VC7 project files until updatedBrian2007-07-211-11/+0
|
* fix bogus recently introduced function param commentsRoland Scheidegger2007-07-201-2/+0
|
* fix mesa's handling of fbo's / window fb (again)Roland Scheidegger2007-07-196-41/+77
| | | | | | | | Make sure the relevant fields in window fbs get updated at appropriate time (those are NOT the same as fbos!!!), and fix up related code accordingly. This is a bit ugly, but there's a reason the issues section in EXT_fbo is a couple hundred pages long... Hopefully correct now.
* more fixes for mesa's fbo handling (fixes tests/fbotest1/2)Roland Scheidegger2007-07-193-3/+14
|
* fix up mesa's probably bogus framebuffer updates with different read/write fbsRoland Scheidegger2007-07-191-12/+26
| | | | | | Conflicts: src/mesa/main/framebuffer.c
* fix mesa fb bindingRoland Scheidegger2007-07-194-7/+12
| | | | | | | | Make sure that we bind the right buffer (draw or read) when rebinding the window framebuffer (the api doesn't allow binding different draw and read buffers at the same time, but the default window framebuffer is basically 2 fb objects, one for read, one for write, which can be different). Pass both of these two down the driver api (no driver uses this right now).
* increase MAX_RELOCS so never run out before batch buffer is full (fixes ↵Roland Scheidegger2007-07-191-1/+1
| | | | xdemos/shape)
* r300: Oops, made a mistake on commit fb4e071beda6e3b9e68a21bbc7649b6c4733c485.Oliver McFadden2007-07-181-2/+2
|
* r300: Cleaned up vertprog construction.Oliver McFadden2007-07-184-369/+383
| | | | | | | | | | | | Construct the vertprog instruction in the 4 DWORD parts... DWORD 0: Opcode and Output. DWORD 1: First Argument. DWORD 2: Second Argument. DWORD 3: Third Argument. Allow the opcode translation functions to generate more than one instruction; useful for when an instruction must be emulated. FLR, XPD, etc.
* r300: Corrected texcoord start when BFC1 is enabled.Tommy Schultz Lassen2007-07-181-1/+1
|
* r300: Corrected some progs/fp/* regressions from the BFC patch.Oliver McFadden2007-07-161-0/+18
| | | | I'm not completely sure this is correct; it restores the old behaviour.
* r300: Use _mesa_num_inst_src_regs for number of arguments.Oliver McFadden2007-07-161-58/+1
|
* r300: Corrected vertprog FLR and XPD instruction regression.Oliver McFadden2007-07-161-10/+15
|
* r300: Added code for vertprog opcode ARL.Oliver McFadden2007-07-161-1/+8
|
* r300: Don't need vertprog scalar flag anymore; it's handled explicitly...Oliver McFadden2007-07-161-12/+8
|
* r300: Removed broken RCC vertprog opcode.Oliver McFadden2007-07-161-14/+0
|
* r300: More vertprog rework; give each opcode it's own function.Oliver McFadden2007-07-161-118/+250
|
* Revert "r300: Gracefully exit after GART memory is exhausted."Oliver McFadden2007-07-161-1/+14
| | | | | | This reverts commit 9457bf62bbba3b9226ebbbea5dc7798ca22485f6. Causes the X server to die with Compiz and Beryl.
* r300: Reorder the vertprog code to the ARB specification.Oliver McFadden2007-07-161-172/+255
|
* fix bogus fb/drawable informationRoland Scheidegger2007-07-161-0/+11
| | | | | | | | | | the framebuffer objects attached to drawables can have invalidate state associated with them, since for the window framebuffer this is per-context state and not per-fbo state. Since drivers rely on that information (otherwise would need to check if currently the window-framebuffer is bound in a lot of places) fix it up in _mesa_make_current (ugly). (Brought over from i915tex_privbuffers, where it fixes xdemos/wincopy when switching to front buffer rendering.)
* fix segfault with i915 drivers in swrast drawpixels path when resizing windowsRoland Scheidegger2007-07-162-0/+12
|
* r300: Use the R300_PVS_UPLOAD_* defines.Oliver McFadden2007-07-163-11/+17
|
* r300: Added the clip plane upload defines.Oliver McFadden2007-07-161-0/+8
|
* r300: Enable the vertprog point size again.Oliver McFadden2007-07-162-6/+5
|
* r300: Corrected position bug with position invariant option. Bug #11594.Oliver McFadden2007-07-161-0/+1
|
* r300: Removed Vim modeline I left in the file by mistake. :-)Oliver McFadden2007-07-161-2/+0
|
* r300: Make sure the modified value of u_temp_i is respected.Oliver McFadden2007-07-161-12/+12
|
* r300: Added a function for vertex program default opcode translation.Oliver McFadden2007-07-161-57/+52
|
* r300: Clean up the vertex program maximum length check.Oliver McFadden2007-07-161-4/+2
|
* r300: Corrected indenting in r300_vertprog.c.Oliver McFadden2007-07-161-47/+50
|
* r300: Major vertex program code clean up and rework.Oliver McFadden2007-07-163-571/+640
|
* r300: Replaced the ugly VERTEX_SHADER_INSTRUCTION typedef.Oliver McFadden2007-07-163-4/+4
|
* r300: Gracefully exit after GART memory is exhausted.Oliver McFadden2007-07-151-14/+1
|
* r300: Disable vertex program point size; it's almost certainly wrong.Oliver McFadden2007-07-141-1/+1
| | | | See the conversation between myself and Tommy Schultz Lassen on mesa3d-dev.
* r300: Clean up the vertex program output assignment.Oliver McFadden2007-07-141-15/+17
|
* nouveau: nv10 and nv11,15 are differentPatrice Mandin2007-07-145-7/+11
|
* fix shader/info string length queries (bug 11588)Jan Dvorak2007-07-131-3/+3
|
* Play "nuke the typedef"Ben Skeggs2007-07-139-27/+34
|
* Revert "r300: Corrected off-by-one error in r300_vertprog.c."Oliver McFadden2007-07-131-1/+1
| | | | This reverts commit 07ac2386f5c0ab9c2432d4b5e3490b1e13d033fc.
* r300: Corrected off-by-one error in r300_vertprog.c.Oliver McFadden2007-07-131-1/+1
|
* r300: Moved some hardware initialization into appropriate functions.Oliver McFadden2007-07-131-27/+26
|
* r300: Use a switch statement in r300UpdateCulling.Oliver McFadden2007-07-131-7/+22
|
* r300: Setup the back facing color bits correctly.Oliver McFadden2007-07-131-5/+6
| | | | | Apparently for back facing color to work you must set all 3 color bits; I guess the hardware cannot handle them separately.
* fix width/depth mix-up (bug 11577)Brian2007-07-121-1/+1
|
* fix swizzle-related bug 11534Brian2007-07-121-2/+3
|
* nv20 also don't support viewport_origin, like nv10Patrice Mandin2007-07-121-2/+2
|
* nouveau: match drm 0.0.9 interfaceBen Skeggs2007-07-122-11/+6
|
* clean-up of stencil codeBrian2007-07-111-50/+35
|
* Minor clean-up of polygon offset logic. Properly compute _MRD field.Brian2007-07-112-20/+24
|