I'm working on re-implementing an application to use mesa-solo with dri.
I'm using a Radeon 9200 SE (rv280), latest CVS drm code and mesa drivers.
In my mesa-solo tests I'm finding that there are two calls to
drmCreateContext. The first is made by the server, and the second is made
by the
Thanks, Stephane. What confuses me is that I'm running all these ioctls as
root. I've done them sudo'd, then as root directly, both from a console
(makes debugging a bit difficult) and via ssh.
Any comment on why the addctx ioctl appears to run to completion (when I
view my dbg statements in
hI -
I'm trying to run linux-solo on Ubuntu 5.10 with kernel 2.6.15.1.
This machine is a PIII and has an AGP radeon 9200SE (Rv280).
I can boot into X and get direct rendering with this kernel and (newly
compiled) modules.
My drm modules are from cvs ca. 1/25/2006
I run the server and test app
I am using mesa-solo in an application that attempts to generate simple
3d scenes at the full frame rate of the video card. I use an /etc/drirc
file with the following option for my app:
option name=vblank_mode value=3/
this option is supposed to synchronize the swap to the VBLANK period.
The file radeon_dri.c sets several defaults in the radeon's private
data.
ctx-driverPrivate = (void *)info;
info-gartFastWrite = RADEON_DEFAULT_AGP_FAST_WRITE;
info-gartSize = RADEON_DEFAULT_AGP_SIZE;
info-gartTexSize= RADEON_DEFAULT_AGP_TEX_SIZE;
info-bufSize =
Just checked out Mesa from CVS and attempted a build. It fails in
src/mesa/drivers/dri/r200 -- portion of build log below.
It appears that there are two files named 'radeon.h' in the -I dirs for
the build of r200_dri.c. One is the one we need, but the other is in the
drm folders. The drm
Problem solved! My mistake - wrong driver being used.
miniglx.conf:
clientDriverName=r200_dri.so (was radeon_dri.so as in distribution file)
D-U-M spells dum. Sorry for the bother.
---
SF email is sponsored by - The IT Product Guide
