Maciej Cencora wrote:
Hi,
here are patches for EXT_fog_coords support for r300-r500 hw. I tested it
only
on rs690 hw (no tcl), so probably I've missed some code for hw tcl path.
Progs
I have tested the fog with:
tests/fog
tests/fogcoord
demos/fogcoord
demos/tunnel
Here's how
http://bugs.freedesktop.org/show_bug.cgi?id=17566
Brian Paul brian.p...@tungstengraphics.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Maciej Cencora wrote:
On poniedziałek, 9 lutego 2009 15:15:53 you wrote:
I gave it a try on a r300 and r500:
tests/fog:
- r300 : all triangles black
- r500: corrupted triangles but correct color
tests/focoord: r300/r500 all triangles white
demos/fogcoord: r300/r500 fog seems ok,
Over the next day or so we're going to merge the gallium-0.2 branch to
master. master and gallium-0.2 are both development branches and
keeping the core Mesa work synced between them is a bit of PITA.
To work out the kinks I'll be pushing a short term
gallium-master-merge branch for
On poniedziałek, 9 lutego 2009 17:40:30 Markus Amsler wrote:
Maciej Cencora wrote:
On poniedziałek, 9 lutego 2009 15:15:53 you wrote:
I gave it a try on a r300 and r500:
tests/fog:
- r300 : all triangles black
- r500: corrupted triangles but correct color
tests/focoord:
Brian Paul wrote:
Over the next day or so we're going to merge the gallium-0.2 branch to
master. master and gallium-0.2 are both development branches and
keeping the core Mesa work synced between them is a bit of PITA.
To work out the kinks I'll be pushing a short term
On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul bri...@vmware.com wrote:
In terms of the build system, we'll initially default to the non-gallium
build. To build with gallium I'll add some new configs like
'linux-gallium'.
I haven't tried building gallium at all, but is there interest in
adding
On Mon, 2009-02-09 at 10:24 -0800, Brian Paul wrote:
Brian Paul wrote:
Over the next day or so we're going to merge the gallium-0.2 branch to
master. master and gallium-0.2 are both development branches and
keeping the core Mesa work synced between them is a bit of PITA.
To work
On Mon, Feb 9, 2009 at 3:28 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul bri...@vmware.com wrote:
In terms of the build system, we'll initially default to the non-gallium
build. To build with gallium I'll add some new configs like
'linux-gallium'.
On Mon, 9 Feb 2009, Kristian Høgsberg wrote:
On Mon, Feb 9, 2009 at 3:28 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul bri...@vmware.com wrote:
In terms of the build system, we'll initially default to the non-gallium
build. To build with gallium
Kristian Høgsberg wrote:
On Mon, Feb 9, 2009 at 3:28 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul bri...@vmware.com wrote:
In terms of the build system, we'll initially default to the non-gallium
build. To build with gallium I'll add some new configs
On Mon, 2009-02-09 at 13:10 -0800, Dave Airlie wrote:
On Mon, 9 Feb 2009, Kristian Høgsberg wrote:
On Mon, Feb 9, 2009 at 3:28 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul bri...@vmware.com wrote:
In terms of the build system, we'll
We can do either:
- have some new build targets, like linux-gallium-dri etc, that
build the drivers and put them in mesa/lib/xyz_dri.so
No not the one we'd like.
or
- build both lots of drivers, and put the gallium ones in a new
directory, like mesa/lib/gallium/xyz_dri.so
I'd suspect
Brian Paul wrote:
Over the next day or so we're going to merge the gallium-0.2 branch to
master. master and gallium-0.2 are both development branches and
keeping the core Mesa work synced between them is a bit of PITA.
To work out the kinks I'll be pushing a short term
Corbin Simpson wrote:
Brian Paul wrote:
Over the next day or so we're going to merge the gallium-0.2 branch to
master. master and gallium-0.2 are both development branches and
keeping the core Mesa work synced between them is a bit of PITA.
To work out the kinks I'll be pushing a short
Hi all,
I'm currently running Intel G35 (i965) hardware with Mesa 7.2 and I've
noticed that sharedtex.c doesn't work.
Apparently it has issues with validating textures from a shared context.
Is this a known bug? Sorry if this has been discussed already.
thanks a bunch~!
sung
On Tue, 2009-02-10 at 01:57 +0100, Anders Juel Jensen wrote:
On Monday 09 February 2009 22:15:44 Keith Whitwell wrote:
but is it possible to build both gallium drivers and classic drivers from
the same tree at the same time?
or is distro life going to be made shit yet again.
17 matches
Mail list logo
