Jerome Glisse wrote:
I think it's related to r300 driver because i get something
with the r300 demo. I get the depth buffer with r300 demo
but not the color one. I think this is due to radeon base address
or to the R300_RB3D_COLOROFFSET0 setup, moreover there
is a need for some endian swapping with get_int & get_short.
So with r300 demo i see what i think is the depth buffer (something
similar to what i got on x86, yellow buffer ...) and have not lock.
With r300 driver glxinfo show strange things & glxgears hard lock
the computer.
I get more things with r300_demo add send a patch (for endian
swapping). You could get a screenshot here to see what i got :
http://dj.planet-d.net/Capture-PPC.png
Which is the normal (as long i remember well what i got on x86 :))
Vladimir you where talking about fbLocation, you think that
r300 driver lock may come from this ?
What i found strange is that the window seems to clear well but
that drawing anything will lock. I will do a sample gl program
to see if only doing glclearbuffer is not locking.
More over Keith who got the driver working on g4 seems to
have the gears drawing in wrong place but clearbuffer in
the correct place, isn't he ?
Thus shouldn't this be linked with the viewport ? or something else ?
By the way there is no swapping like on r200 ?
rmesa->hw.cst.cmd[CST_SE_VAP_CNTL_STATUS] =
#ifdef MESA_BIG_ENDIAN
R200_VC_32BIT_SWAP;
#else
R200_VC_NO_SWAP;
#endif
r200_state_init.c
i keep on looking to that...
best,
Jerome Glisse
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
