| Age | Commit message (Collapse) | Author |
|---|
|
waiting for the DRM to reap them at process exit. Fixes (fatal) allocation
failures in AIGLX configurations.
Reviewed by: Aapo Tahkola
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sw tcl
|
|
- Makes all three drivers use the same screen structure and setup code, with a
few ifdefs for the separate compilation to deal with symbols not being
available to all drivers and the fact that we have no mechanism for dealing
with different config options for different chip families in the same driver.
These issues should be dealt with later.
- Introduces IS_R[123]00_CLASS(radeonScreenPtr) macro for code for taking
different paths depending on the general class of chipset.
- Adds many new R300-class PCI IDs, though not all those listed in
radeon_driver.c.
|
|
|
|
temporaries, parameters, etc).
glGetProgramivARB() now returns all the right things.
Updated i915 and r300 code to initialize program native limits and
current program's native instruction/temporary/etc counts.
|
|
Changes to current operation:
-Elts are no longer converted to 16-bit format
-Cube maps
|
|
This isn't perfect, texcmp still has some issues with the small textures..
but its a good start
|
|
_tnl_vertex_program_stage. Fixes crashes when using vertex programs. Tested on r200 only (fix by Keith Whitwell)
|
|
|
|
Fix suggested by Ian Romanick.
R300 driver now works without segfault.
|
|
_glapi_add_entrypoint has been replaced by a new routine called
_glapi_add_dispatch. This new routine dynamically assignes dispatch offsets
to functions added. This allows IHVs to add support for extension functions
that do not have assigned dispatch offsets.
It also means that a driver has no idea what offset will be assigned to a
function. The vast majority of the changes in this commit account for that.
An additional table, driDispatchRemapTable, is added. Functions not in the
Linux OpenGL ABI (i.e., anything not in GL 1.2 + ARB_multitexture) has a
fixed offset in this new table. The entry in this table specifies the
offset in of the function in the real dispatch table.
The internal interface was also bumped from version 20050725 to 20050727.
This has been tested with various programs in progs/demos on:
radeon (Radeon Mobility M6)
r128 (Rage 128 Pro)
mga (G400)
|
|
for others, and being cleaner with types in fragment/vertex program structures.
One warning in r300_shader.c is still concerning.
|
|
by Idr. This patch is based on Idr patch to radeon driver.
Change #if 1 to #if 0 (r300_context.c:l69) for old dispatch
tab.
|
|
|
|
Use SRC0A instead of WZY/XXX combination for W in XYZ positions.
Remove dodgy hack from POW opcode, now works correctly without it
|
|
generation in Mesa. Requires most recent Mesa cvs to work correctly.
Swizzle code is possibly slow/buggy and will probably be replaced.
Old behaviour can be controlled by a #define in r300_context.h, if
no-one minds I'll remove the old code later on.
Also, disabled cube map extension. AFAIK We don't support it yet,
and it causes issues with UT2004.
|
|
near time.
|
|
using the RADEON_DEBUG environment variable.
|
|
We need to plug in swsetup functions into the TNL module's callbacks.
Also, resize the framebuffer size when the drawable size changes.
|
|
|
|
but it seems to work
|
|
|
|
current Mesa.
|
|
didnt want to build anymore.
|
|
|
|
shading.
|
|
|
|
|
|
correctly disable alpha test. Vertex programs with high vertex count now run a lot faster as software fallback is no longer on. Also disabling 'temp to result'-instructions as they probably violate the spec and dont seem to be something thats needed.
|
|
VSF_MAX_FRAGMENT_LENGTH as it seems a bit low otherwise.
|
|
and some new debugging stuff.
|
|
and fix for glxinfo problem.
|
|
|
|
of trouble.
|
|
|
|
Switch to using R300_EASY_TX_FORMAT() macro everywhere.
|
|
raster functions anyway.
|
|
Hook it up, so lesson06 displays red colored textures.
|
|
- Install custom (though inactive) pipeline
- Track depth test and culling state in hardware registers
|
|
- Scissor support works now
|
|
- Color buffer clear is accelerated, but flickers (possibly caused by a
recent DDX or Mesa change or bad merge)
- Everything else uses software fallback rendering
- There should be no clipping-related artifacts with the
sw-clipspan-fixes.patch against Mesa (posted on dri-devel)
- Multiple clients should be rock solid with a DDX patch that is soon to
come (soon = within the next hour or so)
|
|
|
