Sven Luther [EMAIL PROTECTED] writes:
I've been trying to find specs for implementing hardware RENDER
support for my graphics card. I have the specs for the card. The
problem is that nobody seems to know what the various RENDER functions
in a driver are supposed to do, or what the structs
On Wed, 15 Oct 2003, Alexander Shopov wrote:
Quite frankly... random uninformed people making claims that X
is slow, without any shred of a clue or properly deduced
scientifically measured and reproduceable instrumented data, will
always be out there. We can't stop people from spreading
The _only_ answer that matters is the
technical/scientific one. End users opinions about how things
Technically and scientifically you are right and I agree with you, but
not everyone has the patience for the scientific side. I as sorry as you
are about this thing, but some magic some times
What is funny however, is that any alternative to X, is more or
less functionally useless until someone writes an X server for
it for most general purpose computing.
Well, it would really only /require/ an xlib-compatable interface, but
everybody seems to port XFree86 to run as a client to
CR Benchmarking is a bit like academic tests. It proves that you're good
CR at the benchmark, not at the task.
You can't cheat at a benchmark.
(To be a little bit less cryptical: benchmarks are all we've got to
make sure we're making sense in our design and implementation. In the
right hands,
Kernel modules are not inherently faster. the reason directx (and
openGL) seem so fast on windows is because the manufacturers and MS
tweak the drivers for every last bit of performance. Plus they are
able to utilize interfaces that are not accessable in xfree86 due to IP
concerns. Some xfree86
On Tue, 14 Oct 2003, Alexander Shopov wrote:
Kernel modules are not inherently faster. the reason directx (and
openGL) seem so fast on windows is because the manufacturers and MS
tweak the drivers for every last bit of performance. Plus they are
able to utilize interfaces that are not
Måns Rullgård wrote:
Mike A. Harris [EMAIL PROTECTED] writes:
Right now, the biggest hit on the desktop is probably
unaccelerated RENDER operations. That's what most users likely
see as desktop slowdowns currently. Over time, those things
will improve as people write support.
I've been
François Puitg wrote:
The symptoms are : after X has been started and window manager is up
(it's the same with KDE, GNOME and twm), sometimes after 1 hour, but
most of the time immediately, the keyboard freezes and the mouse
becomes erratic, even when doing nothing, just standing there
Måns Rullgård wrote:
Thomas Winischhofer [EMAIL PROTECTED] writes:
I've been trying to find specs for implementing hardware RENDER
support for my graphics card. I have the specs for the card. The
problem is that nobody seems to know what the various RENDER functions
in a driver are supposed to
I'm not quite convinced that that is an objective comparison
however. Was Quake 3 running in both operating systems with the
exact same 3D settings?
Of course not! ;-) I am as skeptical as you are regarding similar tests.
However - a demonstration like this helps me when proving that X is not
On Wed, 15 Oct 2003 00:19:58 +0300, Alexander Shopov wrote:
I'm not quite convinced that that is an objective comparison
however. Was Quake 3 running in both operating systems with the
exact same 3D settings?
Of course not! ;-) I am as skeptical as you are regarding similar tests.
However
It does no such thing. It demonstrates that OpenGL on Linux is not slow,
but to run those applications you essentially shut down X. You've
demonstrated nothing about X's performance.
I am not sure I understand what you are saying. To the best of my
knowledge - I used the OpenGL drivers that
Apologies for speaking with an antique X server...
What is the latest X version I can get, and what Mandrake/Red Hat distro has
it?
I apologize for complaining, and my original suggestion seems to have caused
quite a ruckus! Kernel modules, indeed! I guess I miss the old days of
DirectX
14 matches
Mail list logo
