[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dri-devel
Subject:    Re: [r200_sanity.c] compilation error
From:       Roland Scheidegger <rscheidegger_lists () hispeed ! ch>
Date:       2006-05-30 1:00:10
Message-ID: 447B991A.1010404 () hispeed ! ch
[Download RAW message or body]

Dieter Nützel wrote:
> Am Dienstag, 30. Mai 2006 00:33 schrieben Sie:
>> Dieter Nützel wrote:
>>> Latest Mesa and DRM CVS:
>>>
>>> r200_sanity.c:163: warning: excess elements in array initializer
>>> r200_sanity.c:163: warning: (near initialization for ‘packet')
>>> r200_sanity.c: In function ‘radeon_emit_veclinear':
>>> r200_sanity.c:945: error: ‘drm_radeon_cmd_header_t' has no member named
>>> ‘veclinear'
>>> r200_sanity.c:948: error: ‘drm_radeon_cmd_header_t' has no member named
>>> ‘veclinear'
>>> r200_sanity.c:948: error: ‘drm_radeon_cmd_header_t' has no member named
>>> ‘veclinear'
>>> r200_sanity.c: In function ‘r200SanityCmdBuffer':
>>> r200_sanity.c:1422: error: ‘RADEON_CMD_VECLINEAR' undeclared (first use
>>> in this function)
>>> r200_sanity.c:1422: error: (Each undeclared identifier is reported only
>>> once r200_sanity.c:1422: error: for each function it appears in.)
>>> make[6]: *** [r200_sanity.o] Fehler 1
>>> make[6]: Leaving directory `/opt/Mesa/src/mesa/drivers/dri/r200'
>> Yes, this is caused by preparation for hw vertex programs on r200. You
>> need a new libdrm (actually, all you need is a new radeon_drm.h) from
>> drm cvs.
> 
> Oh, shit.
> I had latest DRM code but haven't compiled it for some time...;-)
> Works.
> What should I test?
Nothing yet as the code in cvs does pretty much nothing for now. The 
rest is not yet in cvs mostly due to really ugly hacks I needed but 
don't have an explanation for. If you're interested you could try the 
attached patch and try doom3 with the r200 render path (I actually just 
hope it works the same with r200 as with rv250), you still need to 
enable arb_vertex_program manually with driconf. The attached patch is 
basically the same as the earlier one, but without the changes already 
commited to cvs.

> BTW Doom3 do not work any longer on my wife's machine.
> It hangs in 'starting sequence'.
> Log available.
> Duron 1800 (3DNow!, SSE1), 512 MB, r200 (my 'old' one), SuSE 10.0 + latest 
> Mesa/DRM.
> What pre-load should I try.
> Worked some months ago.
Not sure what could be wrong - if that's just the game which hangs (i.e. 
you can still kill it) and you've redirected the output make sure you 
don't forget to specify +set in_tty 0 at the commandline when starting 
doom3, otherwise the game will always stop at "initializing menus".

Roland

["r200vertprogs2.tar.gz" (application/x-tar)]



--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[prev in list] [next in list] [prev in thread] [next in thread]