while trying to activate the 3rd TMU on radeon I discovered that "txr" states get emitted even in the yuvsqare (and multiarb) demo (which use only standard textures): (RADEON_DEBUG=state and yuvsqare demo:) .... radeonBindTexture( 0x8132dc8 ) unit=0 radeonEmitState radeonEmitState - lost context emit TEX/tex-0/9 emit CTX/context/14 skip state TXR/txr-2 skip state TXR/txr-1 skip state TEX/tex-2 skip state TEX/tex-1 emit ZBS/zbias/3 emit MSC/misc/2 emit VPT/viewport/7 emit TXR/txr-0/3 emit MSK/mask/4 emit LIN/line/5 emit SET/setup/5 .... I dont know if its bad, but I think it shouldnt happen.
I changed the CHECK in radeon_state_init.c for txr and
now it doesnt happen anymore, at least in yuvsquare.
radeon_state_init.c:CHECK( txr0, ctx->Texture.Unit[0]._ReallyEnabled & TEXTURE_RECT_BIT)
radeon_state_init.c:CHECK( txr1, ctx->Texture.Unit[1]._ReallyEnabled & TEXTURE_RECT_BIT)
btw. heres also a patch for mplayer vo_gl.c which uses GL_NV_texture_rectangle.
I sent a (sligtly) older version to mplayer-dev-eng, but unfortunately it
got caught by some filter/ wasnt released by the mailinglist moderator.
Interesting. The two other extensions I'd consider useful for this are MESA_ycbcr_texture (yuv textures) and the agp allocator/agp client texturing present in the r200 driver. Does mplayer produce data in a format useable as a ycbcr texture?
Keith
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
