Robert Voigt wrote:
Stephane Marchesin wrote:
Stephane Marchesin wrote:
Hi,
The attached patch adds pci init code for mesa solo with the radeon
driver thanks to a new configuration option in miniglx.conf.
And of course, you're not interested in my debugging printf's. A patch
I noticed that my test programs run at about half the frame rate with
mesa solo than with XFree86 4.3.0 and DRI 20020611 and mesa 4.0.4 (as it
comes with Suse 9.0).
I tested a texture and a long anti-aliased line strip.
This is both with r100 and r200.
I don't think DRI has become slower since t
Jon Smirl wrote:
Mesa-solo does not build with x86 asm turned on and DRI is using x86 asm. It
shouldn't be too hard to make a linux-solo-x86 target.
DRI also includes:
-DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM
That sounds believable. Thank you.
I also believe mesa-solo defaults to
If you build the same *_dri.so for solo and DRI, what happens to
Mesa/src/mesa/drivers/dri/radeon/*/server/*_dri.c ? As I understand it,
they're only used by solo, and derived from and different to the
corresponding files in dri.
I'm asking because if you get solo to use *_dri.c from dri, we wo
When I try to install driconf 0.1.2, I get the following output (similar
with 0.2.2):
python setup.py install
running install
running build
running build_py
running build_scripts
running install_lib
running install_scripts
changing mode of /usr/local/bin/driconf to 755
** (setup.py:5476): WARNING
Felix Kühling wrote:
When I run it, it says (same with 0.1.2 and 0.2.2)
python driconf
Traceback (most recent call last):
File "driconf", line 23, in ?
import driconf
ImportError: No module named driconf
Hmm, the installation should have installed a file named driconf.py in
/usr/local/lib/p
Felix Kühling wrote:
On Mon, 07 Jun 2004 15:52:14 +0200
Robert Voigt <[EMAIL PROTECTED]> wrote:
[snip]
That did it. Now I it starts. It gets to the point where it says
xdriinfo not found, so driconf seems to be ok, only I don't have
xdriinfo. It uses the dri version that came wi
