Hello,
I'm planning to merge gallium-strict-aliasing branch soon, which will
bring another gallium api change.
pipe_reference function has different arguments, because the old version
was pretty much not really useful for strict-aliasing compliant code
(util_color_pack functions also gets an updat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mesa 7.6.1-rc3 available for testing at
ftp://freedesktop.org/pub/mesa/7.6.1/
md5sums:
e3953c0922e106d3bb17d8885aa6b381 MesaDemos-7.6.1-rc3.tar.bz2
7defc7f743df092379e7867c22c806f4 MesaDemos-7.6.1-rc3.tar.gz
24e143039540f744ada492946fea6afa MesaDe
Forwarding...
--- Begin Message ---
It appears that R3xx-R4xx can sample from the Z16 format only. R5xx
should be able to sample from both Z16 and Z24S8.
References:
http://aras-p.info/texts/D3D9GPUHacks.html
Marek
On Tue, Dec 8, 2009 at 12:31 AM, Brian Paul wrote:
> OK, for the MESA_FORMAT_Z2
OK, for the MESA_FORMAT_Z24_S8 case in r300SetDepthTexMode() the
'format' pointer is set to the "X24_Y8" entries.
If you read the comment for X24_Y8 in r300_reg.h it says:
/* These two values are wrong, but they're the only values that
* produce any even vaguely correct results.
Depth/stencil buffer formats is a different thing (already fixed). Currently
the
problem is with depth textures. Formerly driver choose _mesa_texformat_s8_z24
for depth textures (radeonChooseTextureFormat in radeon_texture.c) then in
r300SetDepthTexMode (r300_texstate.c) we set proper hw format
http://bugs.freedesktop.org/show_bug.cgi?id=25500
--- Comment #1 from Robert Schwebel 2009-12-07
13:39:06 PST ---
Created an attachment (id=31828)
--> (http://bugs.freedesktop.org/attachment.cgi?id=31828)
patch to fix the issue
--
Configure bugmail: http://bugs.freedesktop.org/userprefs
http://bugs.freedesktop.org/show_bug.cgi?id=25500
Summary: Add linker option to mklib call
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component:
The main thing is to choose the z/stencil format that's supported by
the hardware. As I mentioned before, it looks like different
generations of ATI/radeon hardware used different formats. It sounds
like that should be resolved now though.
What does piglit's texdepth rendering look like? Wh
http://bugs.freedesktop.org/show_bug.cgi?id=25499
Robert Schwebel changed:
What|Removed |Added
CC||m...@pengutronix.de
--
Configure b
http://bugs.freedesktop.org/show_bug.cgi?id=25499
Summary: Add DESTDIR support to src/gallium/winsys/xlib/Makefile
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: me
Excellent news! Please update site as soon as possible.
Topics are more than interesting. If you have some otherPDF documenation, book,
or other materials (white papers,blueprints, etc.) you want to open to the
public, pleasedo it since it is very important for us who are not at
theepicenter o
Gallium3D Developers,
The videos and slide decks from the Gallium3D Developers Workshop
hosted by VMware on Nov 13th are now being posted online at:
http://www.lunarg.com/wordpress/technologies/gallium-3d/gallium3d-online-developers-workshop/
More of the presentations will be posted to thi
Hi,
Because some hardware under some circumstances (e.g. disabled tiling)
may not be able to use a hardware-specific clear path, it would be
nice to let a state tracker do the clearing by drawing a
screen-aligned quad. I am proposing to change the pipe_context->clear
function to return TRUE if buf
13 matches
Mail list logo
