On Sul, 2004-02-22 at 21:26, Chris Ison wrote:
> these functions out into all the different types so each conversion type is
> done as fast as possible. Looking at it atm, (using my unrelated exprience
> in audio sample format convertion) these could be dramatically spead up by
> doing doing up fun
although I can't find it in mesa, does the r200
drm/dri have a way or method of doing hardware TexSubImage? and if not, does the
specs have infomation on doing hardware TexSubImage.
> Each time texutil_tmp.h is included by texutil.c, eight new functions
> are generated, four for texsubimage2d and four for texsubimage3d.
> Those functions are listed in the arrays seen at lines 488 and 500 of
> texutil_tmp.h
um, apart from partial code duplications, is there any reason not to b
Chris Ison wrote:
ok, looking of the oprofile output of libgl, r200_dri and qw-client-glx,
I decided to hunt for the function
texsubimage2d_bgr888_to_rgba which is at the top of the list at
22.6% of the time.
I have tracked down the function to a define, but from there I don't
know wher
Hi,
I imported the Savage 3D driver from the savage-2-0-0-branch of DRI CVS
into the Mesa trunk. The Savage 2D and DRM drivers on the DRI trunk are
now updated from the savage-2-0-0-branch and I setup Imakefiles in
xc/lib/GL/mesa/drivers/dri/savage to build the 3D driver from Mesa
sources. In othe
ok, looking of the oprofile output of libgl,
r200_dri and qw-client-glx, I decided to hunt for the function
texsubimage2d_bgr888_to_rgba which is at the top of the list at 22.6% of
the time.
I have tracked down the function to a define, but from there I don't know
where it comes from
fr
