Displaying 5 results from an estimated 5 matches for "r300g".
Did you mean:
r300
2010 Jul 15
1
troubles with r300g driver
When trying to run Sins of a Solar Empire (but also some other apps) with r300g driver I have this problem.
"r300: Max size of the constant buffer is 256*4 floats."
followed by big troubles,for example with SoaSe there is broken rendering (everything except menus and control panels is black).
Some time ago it was even worse (crash) so I opened a bug at FDO:
https:/...
2010 May 03
2
_mesa_init_texture_s3tc() vs util_format_s3tc_init()
I am trying to understand the s3tc init code as nv50 gallium has a
problem with that.
It looks like some drivers (r300g and llvmpipe) actually inits s3tc in
two places :
./src/mesa/main/texcompress_s3tc.c _mesa_init_texture_s3tc()
./src/gallium/auxiliary/util/u_format_s3tc.c util_format_s3tc_init()
Here is an extract of the backtrace calls while loading fgfs on llvmpipe :
driCreateScreen -> llvmpipe_create_scree...
2010 May 17
1
nv50 piglit change between 7.8 and master
7.8 branch (533b7663) : 209/246
master branch (c882c31) : 216/241
In short :
8 fail/warn -> pass
5 fail -> skip
1 pass -> fail
So the only regression is glean/clipFlat
Output:
----------------------------------------------------------------------
Test clipping with flat shading (provoking vertex).
clipFlat: Failure for glBegin/End(GL_QUADS), glFrontFace(GL_CCW)
GL_EXT_provoking_vertex
2010 May 21
2
[Mesa-dev] RFC: gallium-msaa branch merge
...> begin with, since a lot of the code could end up with a quad blit which
> really wants RENDER_TARGET/SAMPLER_VIEW bind flags instead).
> It is possible some of the drivers implementation are a bit suboptimal
> now, as they still use surfaces internally for easier migration (svga,
> r300g, nouveau might particularly benefit from some cleanup).
> If a driver implements this just with util_resource_copy_region, it is
> possible there are performance regressions, since some (certainly not
> all) state trackers used a quad blitter instead if this wasn't available.
> The...
2020 May 13
8
[RFC] Deprecate AGP GART support for Radeon/Nouveau/TTM
Unfortunately AGP is still to widely used as we could just drop support for using its GART.
Not using the AGP GART also doesn't mean a loss in functionality since drivers will just fallback to the driver specific PCI GART.
For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available.
Please comment,
Christian.