On Thursday 10 February 2005 14:58, Felix K=FChling wrote:
Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20
[EMAIL PROTECTED]:
On Monday 07 February 2005 15:33, Felix K=3DFChling wrote:
Am Montag, den 07.02.2005, 15:12 +0100 schrieb=3D20
[EMAIL PROTECTED]:
Hardware:
On Saturday 12 February 2005 16:33, Felix K=FChling wrote:
Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20
[EMAIL PROTECTED]:
On Monday 07 February 2005 15:33, Felix K=3DFChling wrote:
Am Montag, den 07.02.2005, 15:12 +0100 schrieb=3D20
[EMAIL PROTECTED]:
[snip]
Tested with
Am Sonntag, den 13.02.2005, 11:03 +0100 schrieb [EMAIL PROTECTED]:
On Saturday 12 February 2005 16:33, Felix K=FChling wrote:
Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20
[EMAIL PROTECTED]:
On Monday 07 February 2005 15:33, Felix K=3DFChling wrote:
Am Montag, den 07.02.2005,
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in this
function)
radeon_screen.c:519: error: (Each undeclared identifier is reported only
once
radeon_screen.c:519: error: for each
Which module is it ? You only need r300 and you can ignore compiling all
others.
best
Vladimir Dergachev
On Sun, 13 Feb 2005, Fionn Behrens wrote:
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
Am Sonntag, den 13.02.2005, 11:28 -0500 schrieb Vladimir Dergachev:
Which module is it ? You only need r300 and you can ignore compiling all
others.
Sorry, here are some more lines.
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in
Weitergeleitete Nachricht
Von: Felix Kuehling [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Betreff: Snapshot build failed
Datum: Sun, 13 Feb 2005 07:41:54 -0800 (PST)
A snapshot build failed at Sun Feb 13 07:41:54 PST 2005. Please inspect the
logfiles in /home/fxkuehl/snapshots/log.
Fionn Behrens wrote:
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in this
function)
radeon_screen.c:519: error: (Each undeclared identifier is reported only
once
Jerome Glisse wrote:
Then I've tried the r300_demo(v_0_0_1): I've wrote an ugly fix that just
works for
me for an endianess problem
Please use lastest r300_demo as i commited patch
for big endian PPC. Anyway help is welcome for PPC :)
From the actual Makefile:
CFILES=r300_demo.c r300_lib.c
On Sun, 2005-02-13 at 18:38 +0100, Felix Khling wrote:
r200_screen.c: In function `r200CreateScreen':
r200_screen.c:407: error: `addr' undeclared (first use in this function)
Whoops, my bad, should be fixed now. I wonder how that built for me...
--
Earthling Michel Dnzer | Debian
Ben Skeggs wrote:
Hello,
I've attached a patch with a port of the r200 vertex buffer code for the
r300 driver.
The performance of the vertex buffer codepath is now roughly the same as
the
immediate path, and tuxracer now seems to be rendered almost correctly.
I've tried it on ppc, it works very
Dario Laera wrote:
Ben Skeggs wrote:
Hello,
I've attached a patch with a port of the r200 vertex buffer code for
the r300 driver.
The performance of the vertex buffer codepath is now roughly the same
as the
immediate path, and tuxracer now seems to be rendered almost correctly.
I've tried it on
On Sun, 13 Feb 2005 18:22:43 +0100, Dario Laera [EMAIL PROTECTED] wrote:
Jerome Glisse wrote:
Then I've tried the r300_demo(v_0_0_1): I've wrote an ugly fix that just
works for
me for an endianess problem
Please use lastest r300_demo as i commited patch
for big endian PPC. Anyway help
On Sun, 13 Feb 2005 20:14:20 +0100, Dario Laera [EMAIL PROTECTED] wrote:
I've tried it on ppc, it works very well, now I get 1000 fps in vb path
against 750 with immediate path.
About tuxracer I'm getting the same result as some days ago:
http://laera.web.cs.unibo.it/dri/tuxracer.png
I know
On Sun, 13 Feb 2005 19:02:40 +0100, Dario Laera [EMAIL PROTECTED] wrote:
Fionn Behrens wrote:
--- Mesa/src/mesa/drivers/dri/radeon/server/radeon_macros.h 2005-02-12
21:37:07.0 +0100
+++ Mesa.up/src/mesa/drivers/dri/radeon/server/radeon_macros.h 2005-02-13
17:24:40.288843552
These are the games I've tried with the latest CVS from this afternoon:
Neverputt and neverball play, but some debug output gets displayed:
*WARN_ONCE*
File r300_state.c function r300GenerateTexturePixelShader line 1600
Jerome Glisse wrote:
Do you have lastest Mesa checkout ? Maybe Michel
has applied the wrong patch to mesa cvs. I will check
this.
I've cvs-ed it this afternoon, but looking to Re: [Fwd: Snapshot build
failed] seems that michel will fix it soon.
--
Laera Dario
Undergraduate student at Computer
On Sat, 2005-02-12 at 23:56 -0500, Michel Dänzer wrote:
On Sun, 2005-02-13 at 15:16 +1100, Benjamin Herrenschmidt wrote:
Those are still incorrect as they totally lack memory barriers...
INREG() doesn't (or does it?), and it's the only one used by the 3D
drivers.
Hrm.. in fact, you are
Hello,
These are the games I've tried with the latest CVS from this afternoon:
Neverputt and neverball play, but some debug output gets displayed:
--snip-- :p
You can get neverball working much more smootly by switching everything
to low in the menu screen. Ignore the warn once messages, they're
UT, Marbleblast, and Orbz) die with:
r300_check_render: fallback:ctx-Texture.Unit[i].Enabled
Could you disable multitexturing in these games ?
GLTron and Blender die with:
r300_check_render: fallback:ctx-Line.SmoothFlag
Don't know about this one - see what happens when you comment out this
Am Sonntag, den 13.02.2005, 13:39 -0500 schrieb Michel Dänzer:
On Sun, 2005-02-13 at 18:38 +0100, Felix Kühling wrote:
r200_screen.c: In function `r200CreateScreen':
r200_screen.c:407: error: `addr' undeclared (first use in this function)
Whoops, my bad, should be fixed now. I wonder
Hi,
Attached is patch, an ugly hack that should give
you texture on ppc, at least here i got texture and
could play to tuxracer and see glexcess (i don't
think there is a q3 for ppc on linux thus i test
with glexcess and few others progs). So please
test it and tell me the result :)
What i still
On Mon, 2005-02-14 at 09:07 +1100, Benjamin Herrenschmidt wrote:
On Sat, 2005-02-12 at 23:56 -0500, Michel Dnzer wrote:
On Sun, 2005-02-13 at 15:16 +1100, Benjamin Herrenschmidt wrote:
Those are still incorrect as they totally lack memory barriers...
INREG() doesn't (or does it?),
On Sun, 2005-02-13 at 19:25 -0500, Michel Dänzer wrote:
On Mon, 2005-02-14 at 09:07 +1100, Benjamin Herrenschmidt wrote:
On Sat, 2005-02-12 at 23:56 -0500, Michel Dänzer wrote:
On Sun, 2005-02-13 at 15:16 +1100, Benjamin Herrenschmidt wrote:
Those are still incorrect as they totally
Hi Jerome,
I am a bit puzzled with your patch - do you really need to hard code
format field in r300_state.c ?
If not, please commit the modification for the texture format
table, it looks fine to me. (and not really a hack ;) )
best
Vladimir Dergachev writes:
I am a bit puzzled with your patch - do you really need to hard code
format field in r300_state.c ?
I find that with that line there, it works moderately well (textures
look mostly correct although dithered at the edges), but with that
line commented out, textures
26 matches
Mail list logo
