| Age | Commit message (Collapse) | Author |
|---|
|
waiting for the engine to idle. There's no way for another buffer to
become free anyway once the engine is idle.
|
|
|
|
tuxracer should render correctly. Immediate path was left enabled.
|
|
problems with initial zbias...
|
|
clears and other things not to work. This bug can be triggered by extending struct r300_hw_state by two struct r300_state_atom's from its current size. Everything zbs and unk42B4 related is now covered with HAVE_ZBS and GA ifdefs. Who wants to fix it? Not i. :)
|
|
mode colorbuffer clears are still mysticly broken by offsets... Maybe we need to merge zbs and unk42B4 together?
|
|
|
|
Change Polygon.OffsetFill from fallback to warn once.
Quake demo now works, modulo texture rendering issues due to absent pixel shader pipeline.
|
|
|
|
Looks like the matter of texture formats is a lot simpler, with the wrong
display in quake explained by the fact that we are not handling texture combine modes.
|
|
in the r300_run_immediate_render function.
Bumps up glxgears fps count by about 100 points.
|
|
This can be tested with lesson19 from NeHe.
This has also shown that the alpha code does not work - we pick up a red tint
for transparent pixels somewhere.
|
|
* move proven code into the r300_state.c
* update ClearBuffer to cope with more dynamic state
* cleanup !
|
|
Hook it up, so lesson06 displays red colored textures.
|
|
- Install custom (though inactive) pipeline
- Track depth test and culling state in hardware registers
|
|
|
|
|
|
- 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)
|
|
|
