Perhaps this was caused by the debug info stripping.
I've just ran `strip --strip-debug` to everything. Does anybody know if
this can break anything?
Sergey, I've put in the same place the libGlcore.a without scripting so
that you can check it that changes anything. Unfortunatly is not very
On 2001.12.10 23:17 Sergey V. Udaltsov wrote:
Try the tunnel demo. For me it went from 0.7fps to 25fps.
For me, numbers are similar. Though, there are problems with fog: tunnel
cannot turn it on (in fact, nothing happens on f - the fog is always
off). For pre-pre-pre-alpha, this is not
On 2002.01.18 16:55 Jose Fonseca wrote:
...
The first idea can be put in practice right now. It's an excellent
opportunity for me to learn about DRI and make a contribution at the
same time. With that in mind I've developed a quick python script to
dump all the dri-devel into a standard
. What
do the elder developers think?
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https
there`s more of the same. The XMesa code used for indirect/software
rendering was originally borrowed from stand-alone Mesa and its
pseudo GLX implementation. There are some crufty side-effects from
that.6. Authorship and Acknowledgments.This FAQ is compiled and maintained by José Fonseca,
[EMAIL PROTE
Before I start including copyrighted stuff from the existing DRI
documentation I would like get permission from the copyright owners. I'm
refering to:
Hardware Locking for the Direct Rendering Infrastructure
The Direct Rendering Manager: Kernel Support for the Direct Rendering
Infrastructure
On 2002.01.21 00:41 Philip Brown wrote:
On Sun, Jan 20, 2002 at 07:17:40AM -0800, Gareth Hughes wrote:
Philip Brown wrote:
but I would say that microsoft DOES want to kill OpenGL,
...
Allen's original statement made the point that MS considers OpenGL
to be dead and buried, period.
Peter,
On 2002.01.22 03:43 Peter Surda wrote:
Hi!
I hope I'm not gonna be completely offtopic, but I wanted to say that it
isn't
You're not being offtopic. In fact this topic has been quite discussed
lately.
necessary to have 10+ years of X experience to contribute useful code to
DRI
On 2002.01.21 22:37 Ian D Romanick wrote:
On Sun, Jan 20, 2002 at 06:20:25PM +, José Fonseca wrote:
I've finished compiling the the information gathered from the dri-devel
archives into the FAQ.
Even if the answers aren't available yet, a section should be added
.
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
The IRC log says 18:00 GMT. That is 25min from now.
Regards,
Jose Fonseca
On 2002.01.28 17:24 Sottek, Matthew J wrote:
When did we plan on doing the IRC meeting? I missed the final
decision.
-Matt
-Original Message-
From: Daryll Strauss [mailto:[EMAIL PROTECTED]]
Sent:
Darryl,
On 2002.03.02 01:05 Darryl Cording wrote:
Hi Jose,
...
I am using the source code and was wondering if I could simply unpack
the mach64 branch over the top of a X4.2 tree
and still get a working system after a compile. I tried it and it seemed
to compile OK but I had
Frank,
On 2002.02.05 05:28 Frank Worsley wrote:
I have placed a link from the Doc page to your developer FAQ.
Thanks.
The log of the second meeting as well as a breef summary was posted by
Marcelo Magallon
on the 28th. I think you should be able to pick it up on the archive.
.).
--
Frank Earl
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists
Hi,
I've included an (hopefully) updated version the Mesa Implementation Notes
in the DRI-Devel-FAQ.
I would appreciate corrections additions to this.
Although a hypertext version (whith direct links to the DRI CVS) is at
...
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.02.10 09:31 Gareth Hughes wrote:
...
These chips can read
and write arbitrary locations in system memory. For all chips that
have this feature, the only safe way to program them is from within
Which of the chips currently supported by DRI is more similar in this [DMA
programming]
testing specific features.
Regards,
Leif
Good work, Leif.
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL
be.
When you're more sure were the problem is, you can then try using a remote
kernel debugger to step trhough the code and understand the failure
mechanism, or simply add even more debug output statements.
Oh, and of course, having a journaled file system.
Regards,
José Fonseca
I'm going to do what ask for! :-)
I'll post here when it's done.
Cheers,
Sergey
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri
already done that I can
base upon for automate this taks?
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED
not as it is configured,
because it just builds part of the tree (therefore the need to lndir
/usr/X11R6 to /usr/X11R6-DRI). Nevertheless you don't need it.
Thank you very much for any help,
Michael
Regards,
José Fonseca
_
Do You Yahoo!?
Get your
/X11R6/bin/glxinfo' and also 'ldd /usr/X11R6/bin/glxgears' (paths
may vary).
DRI definitely works with Quake3, that is really strange...
Thanks for the help!
Michael
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com
,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
you more, but at least you know what the problem
is and how to circunvent it for the time being, allowing you to fully
enjoy the (yet rather limited) capabilities of the mach64 DRI driver.
Regards,
José Fonseca
_
Do You Yahoo!?
Get your
On 2002.02.20 02:07 Keith Whitwell wrote:
José Fonseca wrote:
...
Trunk:
For the drivers at the trunk I'll assume that the user will have XFree
4.2.0 so it will only be necessary to pack:
- the DDX driver (/usr/X11R6/lib/modules/drivers/*_drv.o)
- the Mesa driver (/usr/X11R6
has a
nice set of OpenGL demos.
Thanks,
Michael
Regards,
José Fonseca
UnrealTournament.ini
Description: Binary data
are seen then, not
interely at least.
I never understood very well why there are some 3D graphics cards
benchmarks/reviews that advertise an absurd number of fps.
What is the point of sustaining such a frame rate that has no pratical
advantage?
José Fonseca
switch VT while running an OpenGL application on mach64 as it is
now.
Cheers,
Sergey
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
an OpenGL application on mach64 as it
is
now.
Well. I wont do it any more:)
Big thanks for comments
Sergey
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On 2002.02.22 20:57 Alan Hourihane wrote:
On Fri, Feb 22, 2002 at 08:37:08PM +, Keith Whitwell wrote:
Jos Fonseca wrote:
On 2002.02.22 17:28 Keith Whitwell wrote:
...
What is libGLcore.a? Is that actually used?
Keith
Is responsible for the indirect
On 2002.02.22 22:02 Alan Hourihane wrote:
On Fri, Feb 22, 2002 at 09:38:28PM +, José Fonseca wrote:
No. XFree86 4.2.0 is Mesa 3.4.x based, and it seems XFree86 4.3.0 will
be Mesa 4.0.x based. A MAJOR update!
Alan.
hmmm.. the only way I see to make everyone happy (I'm
it be
compatible with XFree 4.2.0? Or Mesa 4.0-compatibility makes this
impossible?
Cheers,
Sergey
They will be compatible because they overwrite libGL.
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http
I have a web statistics package on my webserver
http://mefriss1.swan.ac.uk/cgi-bin/awstats.pl were one could get that
information.
This doesn't mean that I won't put my stuff on DRI website: I've sent an
email to Frank and I'm waiting for his reply.
José Fonseca
but 'strip' always removed crucial symbols, no matter what.
Only if I have two build trees: with and without debugging info.
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On 2002.02.22 22:49 Daryll Strauss wrote:
On Fri, Feb 22, 2002 at 10:24:49PM +, José Fonseca wrote:
I have a web statistics package on my webserver
http://mefriss1.swan.ac.uk/cgi-bin/awstats.pl were one could get that
information.
This doesn't mean that I won't put my stuff on DRI
every optimization in
Mesa on CVS, since the processor abilities are checked on runtime.
Does anyone see a problem with this?
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On 2002.02.26 13:19 Alan Hourihane wrote:
On Tue, Feb 26, 2002 at 01:06:17PM +, José Fonseca wrote:
I have just merged the trunk into my mach64-0-0-2-branch making
cvs update -kk -d -P -j HEAD
and I solved most of the conflicts, but I noticed that this is still
not
enough
On 2002.02.26 13:41 Alan Hourihane wrote:
On Tue, Feb 26, 2002 at 01:32:39PM +, José Fonseca wrote:
On 2002.02.26 13:19 Alan Hourihane wrote:
...
Your better off creating a branch from the trunk and merging your work
over that way. Seeing as the mach64-0-0-1 branch is still Mesa 3.4
and rules to do
that.
I hope between the next 5 hrs, or the next morning in the worst case, to
commit. I'll get back to you then.
Regards,
José Fonseca
On 26 Feb 2002, Jose Fonseca wrote:
Well, I'm answering to my own question, just in case someone is also
interested!
I've finished
It's done. At least, the trivial changes are made. There is still problems
in the DDX due to changes in the XFree 4.2.0 tree, and in the Mesa 3D
driver.
On 2002.02.26 21:01 Leif Delgass wrote:
On Tue, 26 Feb 2002, José Fonseca wrote:
Leif,
On 2002.02.26 19:35 Leif Delgass wrote:
So
On 2002.02.27 01:23 Leif Delgass wrote:
On Tue, 26 Feb 2002, José Fonseca wrote:
It's done. At least, the trivial changes are made. There is still
problems
in the DDX due to changes in the XFree 4.2.0 tree, and in the Mesa 3D
driver.
I thought there were only mininal changes
.
Please share your thoughts regarding this.
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https
Since my last reached the list I'm sending this one again. I hope it
doesn't get duplicated though.
It seems that there are some problems on the i8x0 DRM drivers with recent
kernels as stated below.
José Fonseca
On 2002.02.27 16:19 Thomas Dodd wrote:
Jose Fonseca wrote:
Luckily, after
, texObj, t );
}
t = (r128TexObjPtr) CALLOC_STRUCT( r128_tex_obj );
if (!t)
return NULL;
Instead it should be:
fprintf( stderr, __FUNCTION__( %p )\n, texObj);
If there is no objections and if nobody else does it before I'll commit
this myself.
Regards,
José Fonseca
Regards,
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.03.01 07:25 Leif Delgass wrote:
I've commited the last major chunk of the Mesa 4 merge, mainly in
mach64_tris.c. The branch should now compile and run, but it needs
debugging, as glxgears is still segfaulting.
That's great Leif!
I'm working on it. It seems that the problem is on
.
Regards,
José Fonseca
On 2002.02.28 20:38 Sergey V. Udaltsov wrote:
...
Just hope, after all these wonderful texture-related changes, you wont
forget to update (and notify us testers) binary snapshots:)
Cheers,
Sergey
PS Thank for new slim tarballs. Less then 2 megs - it is cool
On 2002.03.01 18:30 Leif Delgass wrote:
On Fri, 1 Mar 2002, José Fonseca wrote:
I've overcome this, but sursprisingly there is no further segfault. I
see
all the debuging statements scrolling in my terminal without stoping.
This either means that the problem is at the locking
going to see if I can get another laptop from a friend of
mine to make further debugging.
José Fonseca
On 2002.03.01 17:35 José Fonseca wrote:
Have no idea. I'm still having troubles disabling the lock, because some
of the state variables are set up when the card is locked (cliprects
e.g
pointers can also be overwritten with those in the sw_* modules
to fallback to software rendering.
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel
more easily since they don't
come in so many shapes as the vertexes do.
José Fonseca
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
Dri-devel mailing list
[EMAIL
: /* VERTEX_1_XY */
0020: (MACH64_VERTEX_1_SECONDARY_S) | (216) /* setup for programming
three sequential registers */
0024: /* VERTEX_1_SECONDARY_S */
0028: /* VERTEX_1_SECONDARY_T */
002c: /* VERTEX_1_SECONDARY_W */
0030: ...
...
José
On 2002.03.04 18:51 Leif Delgass wrote:
On Mon, 4 Mar 2002, José Fonseca wrote:
Although I had no idea of the consequences, I changed this value to 9
(the
minimum seen in other drivers) which made some of the textures appear,
though they had several problems (they were tiled
On 2002.03.04 19:13 Leif Delgass wrote:
On Mon, 4 Mar 2002, José Fonseca wrote:
But why does the number of levels has to do with the maximum texture
size?
As I understand it, a mipmapped texture is composed of several levels,
which are copies of the texture at different
file itself, but I'm
must be doing something wrong because the results are different and none
is what is should be.
My machine locked hard when running multiarb, but there was no message on
the sys log.
José Fonseca
___
Dri-devel mailing list
[EMAIL
On 2002.03.06 13:17 Keith Whitwell wrote:
José Fonseca wrote:
...
In the end I come up to the conclusion that this is neither one is the
way
to do it:
- Premultipling in the _emit function is not enough because clipping is
made after. Even if we premultiply the interpolation
too much time and wasn't getting nowhere
since the X didn't even started properly. When I get some more time I try
to repeat the changes incrementally to see whats's breaking.
Regards,
José Fonseca
PS: It's sad to know that mipmapping is really broken, but it was nice
that you made that check
building has been working quite well lately, so I plan
to devise a way to upload them to the DRI website, and perhaps even using
the SF compiler farm.
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net
be worthfull for those who can to
try them and get some insight as you said.
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
.swan.ac.uk/~jfonseca/dri/mailing-lists/
I hope this helps.
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.03.10 15:55 Frank C. Earl wrote:
On Sunday 10 March 2002 11:44 am, José Fonseca wrote:
...
Sorry for being silent for so long gang. Been, yet again, crushed under
with lovely personal business. I have started a new branch
(mach64-0-0-3-dma-branch), and I'm actually putting
agree with you and I don't plan
to look deeper into it until other things are supported, but since Ian ran
into this by accident and brought the subject up, I also found it was a
good oppurtinity to discuss it to be able establish some roadmap.
Regards,
José Fonseca
to X11R6-DRI - everything is
fine (more or less, to the current state of the driver).
Yes, libGL should be using /usr/X11R6 indeed. I'm going to take libGL out
of binary packages, as Jens did, so that this problem is no longer an
issue.
Thanks for the help.
Cheers,
Sergey
José Fonseca
.
Cheers,
Sergey
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
.
Is this the kind of performance that one can expect from a PIO only card
(I'm thinking of tdfx for example here)?
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
is too much, it's always good to have
more than just the latest snapshot since the trunk could go havoc
sometimes.
Does the the dynamic HTML code in the download page handle this?
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https
didn't have time to really start X because
it's pretty late here (as you can see by the build time).
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/bleeding-edge/mach64-20020314-0123-i386-Linux.tar.bz2
Cheers,
Sergey
Regards,
José Fonseca
ICQ:66024647
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
line information, isn't
it? Does anybody have any alternative idea?
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
to test/develop... - I'm so bad! But after all, I'm just
preparing him to the future, Linux that is! ;o).
Bottom line: _please_ keep us posted on your advances on Savage4, as I'll
do when that time comes. Otherwise, there will be unnecessary work
duplication.
Regards,
José Fonseca
PS
good taste ; )
Could you tell me what psx emulator are you using under linux? I'm curious
about it...
Vale,
- max
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
,
Sergey
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
ran into lack of free hd space...
...
--
Leif Delgass
http://www.retinalburn.net
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
is not refreshed
properly and things are drawn over the previous frame. When I run again
this doesn't happen anymore. This seems that some state vars still aren't
being updated properly.
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https
1750CDT.
David Bronaugh
Unfortunately the tuxracer source code isn't of much help, since the tux
geometry is created by an embebed tcl interpreter from a script, so it's
not obvious the what's the state when it's being drawn.
José Fonseca
___
Dri
the flickering light cycle and trail gap in gltron with alpha
blending enabled.
--
Leif Delgass
http://www.retinalburn.net
Great work, Leif!
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri
possible to make it usefull for simple
realtime rendering. Regards,
José Fonseca
Index: swrast/s_blend.c
===
RCS file: /cvsroot/mesa3d/Mesa/src/swrast/s_blend.c,v
retrieving revision 1.14
diff -u -r1.14 s_blend.c
--- swrast/s_blend.c
,
Sergey
I erroneously updated the install.sh script of the trunk snapshots instead
of the mach64.
From this moment both should be doing lddconfig only when stricly needed,
hopefully.
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED
On 2002.04.03 13:07 Marcelo E. Magallon wrote:
[are the mailing lists having hiccups? I sent something yesterday and it
didn't show up]
José Fonseca [EMAIL PROTECTED] writes:
+#if 0
#define DIV255(X) (((X) 8) + (X) + 256) 16
+#else
+ const GLint temp;
+#define
and incorrect rendering. Probably, it's buggy app
(version 0.1.2:) but not necessarily. Could anyone please try and
comment an experience?
Cheers,
Sergey
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net
.
I'll check it.
Cheers,
Sergey
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.04.04 09:08 Keith Whitwell wrote:
On Thu, 4 Apr 2002 01:56:22 +0100
José Fonseca [EMAIL PROTECTED] wrote:
...
the further away is the vertex more its color is nearer to the fog
background color. Since the colors are interpolated in the triangle
this
gave the impression
as I
return from vacations (next Monday).
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.04.04 18:47 Tony Rogvall wrote:
José Fonseca wrote:
On 2002.04.04 11:46 Tony Rogvall wrote:
...
Found it, I assumed it was a printk and removed DRM_INFO voila it
started
without
a crash. In mach64_dma there is code for printing AGP_BASE !! Just
put
some
trick in the C code, but it will stay on hold because I
feel I have to dedicate myself to mach64 again.
Regards,
José Fonseca
PS: I've CC'd to dri-devel because this subject was first raised on the
DRI meeting, but I'm not sure if there is a real interest since most of
its subscribers
On 2002.04.09 23:02 Jens Owen wrote:
Jens Owen wrote:
versioning and header names are done. I'm freezing now and will start
the merge process.
Merge to trunk done. drmcommand-0-0-1-branch is now dead.
What are the effects of this on the package and installations scripts?
José
trunk soon. This way there are less
places to fix eventual bugs.
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
on the C code as rejected by glean...
Thanks for you work!
-Brian
Regards,
José Fonseca
#include stdio.h
#include stdlib.h
int main()
{
unsigned short p, q, a;
unsigned c1 = 0, c2 = 0, c3 = 0, c4 = 0;
for (p = 0; p = 255; ++p)
for (q = 0; q = 255; ++q)
for (a = 0; a = 255
forward to hear some news from mach64 front.
Regards,
Sergey
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
in Linux but I really don't know...
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
it will
be done shortly.
I'm still not sure if everything is in place for DRI on Mach64 PCI cards.
I'm in the process of updating and recompiling the kernel to have agpgart
as a module to be able to check it myself.
Regards,
José Fonseca
___
Dri-devel
of debugging, which took much more time than this.
Thanks
Graeme
Regards,
José Fonseca
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
In the following of last IRC meeting, here is a draft of a FAQ with what
was said. Comments are welcome.
Regards,
José Fonseca
Binary compatibility
1. What does binary compatibility means?
It means that that driver binaries made on previous releases
should
On 2002.04.11 01:40 José Fonseca wrote:
...
There is still missing support for PCI operation of an AGP card when
agpgart isn't available - not much really - just a question of
book-keeping so it will be done shortly.
Done.
I'm still not sure if everything is in place for DRI on Mach64
On 2002.04.10 19:40 José Fonseca wrote:
... since the specs give some tolerance it would be nice to run the
conformance tests with different settings in mmx_blend.S, specially the
single multiply w/o rouding ...
I've started to play with glean and I tried to check this myself
On 2002.04.12 14:43 José Fonseca wrote:
On 2002.04.10 19:40 José Fonseca wrote:
... since the specs give some tolerance it would be nice to run the
conformance tests with different settings in mmx_blend.S, specially the
single multiply w/o rouding ...
I've started to play with glean
On 2002.04.12 18:26 Allen Akin wrote:
On Fri, Apr 12, 2002 at 02:43:00PM +0100, José Fonseca wrote:
|
| I've started to play with glean and I tried to check this myself, but
it
| seems there is no effect in the results no matter what changes I make
in
| mmx_blend.S. ...
The blend test
On 2002.04.12 19:20 Allen Akin wrote:
... It might be related to deep color channels, or possibly
to glean tests other than the basic blending tests. ...
That was it. I'm really sorry for all the fuzz, I just remembered I'm
probably the last one on earth using 16bit depth! Of course the
in wonderful discoveries..
José Fonseca
PS: In case you're wandering if all these details do really matter so
much, most of the stuff here will apply to the C code optimizations as
well. And don't forget that when the 64bit processors get into our homes
we can make what is being done now on MMX code
1 - 100 of 364 matches
Mail list logo
