From: Andreas S. <A.S...@gm...> - 2003-06-10 11:22:29
|
Am 2003.06.10 12:12:56 +0200 schrieb(en) Keith Whitwell: > Keith Whitwell wrote: >> Andreas Stenglein wrote: >>=20 >>> @keithw: here is another version. >>>=20 >>> yuvrect.c seems to work >>> texrect.c still doesnt work >>>=20 >>> any hints? >>=20 >=20 > OK, the final piece of the puzzle fell into place. Without the=20 > radeon docs you might hav had trouble find this -- basically, the=20 > radeon still expects texture rectangle texcoords to be in 0..1=20 > range, rather than 0..width,0..height like the r200. >=20 > I haven't got the code running for this yet, but modifying the app=20 > to supply the texcoords the hardware expects gives a good image. >=20 > Keith >=20 yes, its unbelievable... it works with texcoords 0...1 ;) 1) Do you have an idea how to make it work with the right texcoords? 2) Since the default bordermode GL_REPEAT doesnt work/isnt allowed with npot textures, should there something be done about that? 3) in radeon_ioctl.c, function radeonEmitVbufPrim() the first cmd is cleared before filled with the cmd_type: cmd[0].i =3D 0; cmd[0].header.cmd_type =3D RADEON_CMD_PACKET3_CLIP; .... should this be done in radeonEmitBlit() also or is that not necessary? 4) I missed a line in radeon_context.c: driCalculateMaxTextureLevels( rmesa->texture_heaps, rmesa->nr_heaps, & ctx->Const, 4, 11, /* max 2D texture size is=20 2048x2048 */ 0, /* 3D textures unsupported. */ 0, /* cube textures unsupported. */ =3D=3D=3D> 11, /* max texture rectangle size is=20 2048x2048 */ 12, GL_FALSE ); regards, Andreas |