The Linux Kongress is accepting applications for fully sponsered
workshops. This is an opportunity for OS development communities to get
together and work face to face for 3 days. See
http://www.linux-kongress.org/2002/workshops/faq.html for more details.
If you are interested in attending
Jens Owen wrote:
The Linux Kongress is accepting applications for fully sponsered
workshops. This is an opportunity for OS development communities to get
together and work face to face for 3 days. See
http://www.linux-kongress.org/2002/workshops/faq.html for more details.
If you are
Hi!
I just checked out and compiled the r200-0-1-branch:
glxgears: ~ 1650 fps
I've just commited a small optimization that gears benefits from. It
may be quite close now...
its about 1720 now ;-)
[...]
A large part of this difference is presumably due to HyperZ - something
that
Adam K Kirchhoff wrote:
Actually, Jens, I'm not even talking about getting it working with
Xinerama. Just a traditional dualhead setup with two independent
displays. Last time I tried this, the radeon driver disabled DRI.
The traditional dualhead setup with two independent displays from
Leif Delgass wrote:
After merging the trunk into the mach64 branch, I get a segfault in the
Xserver in DRIClipNotify (dereferences a null pointer when trying to call
a wrapper function, I think) if direct rendering is disabled after
DRIFinishScreenInit is called, e.g. if the init of the drm
Jens Owen wrote:
The Linux Kongress is accepting applications for fully sponsered
workshops. This is an opportunity for OS development communities to get
together and work face to face for 3 days. See
http://www.linux-kongress.org/2002/workshops/faq.html for more details.
If you are
Could you give a quick explanation, just for my understanding, of the
differences between the dualhead Matrox cards (which support the DRI on
the primary head) and the dualhead Radeon cards (which do not, currently).
Adam
On Fri, 5 Jul 2002, Jens Owen wrote:
Adam K Kirchhoff wrote:
Adam K Kirchhoff wrote:
Could you give a quick explanation, just for my understanding, of the
differences between the dualhead Matrox cards (which support the DRI on
the primary head) and the dualhead Radeon cards (which do not, currently).
DRI requires a hardware cursor. Matrox does not
On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
However, I think you may be tickling a latent bug in the DRI. It's
possible that all the other drives have just avoided this bug so far.
I looked at DRICloseScreen and I don't see that the DRIClipNotify
wrapper is being removed. There are
Leif Delgass wrote:
On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
However, I think you may be tickling a latent bug in the DRI. It's
possible that all the other drives have just avoided this bug so far.
I looked at DRICloseScreen and I don't see that the DRIClipNotify
wrapper is being
On Fri, 5 Jul 2002, Jens Owen wrote:
Leif Delgass wrote:
On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
However, I think you may be tickling a latent bug in the DRI. It's
possible that all the other drives have just avoided this bug so far.
I looked at DRICloseScreen and I
Hi,
I have been playing with the new binary radeon 8500 drivers. Most
applications work fine but
I have experienced problems with the following applications:
o RTCW: A lot slower that with my old banshee but that could just be
because I am running
out of memory (128Mo is obviously not enough
On Fri, 2002-07-05 at 14:55, Stefan Lange wrote:
on more comment: xv seems to be broken, it only gives me a black overlay
window with mplayer. are there plans to merge with gatos some time?
http://www.keithp.com/~keithp/download/radeon_video.diff makes Xv work
with all Radeon chips.
Leif Delgass wrote:
On Fri, 5 Jul 2002, Jens Owen wrote:
Leif Delgass wrote:
On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
However, I think you may be tickling a latent bug in the DRI. It's
possible that all the other drives have just avoided this bug so far.
I looked at
I get seg fault (core dumped) running glxgears.
System:
FreeBSD 4.5-RELEASE, cards banshee, using glide3 ports.
Glxinfo says DRI is enabled.
Simon
---
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
On Fri, 5 Jul 2002, Jens Owen wrote:
[...]
The xc/config/cf/host.def in the DRI tree is setup to easily modified to
build a debuggable server. Attached is a copy of a modified host.def
file I used for debugging an i810 problem. You'll probably need to add
the mach64 driver to these
On Friday 05 July 2002 10:39, Alan Hourihane wrote:
On Fri, Jul 05, 2002 at 12:26:28 +0100, Keith Whitwell wrote:
With this, I think it's time to merge. Would anyone else be willing to
do it? (since I missed some stuff last time, like those id changes.
I'm not sure how those are to be
On Fri, 2002-07-05 at 17:00, Simon Cahuk wrote:
I get seg fault (core dumped) running glxgears.
System:
FreeBSD 4.5-RELEASE, cards banshee, using glide3 ports.
Glxinfo says DRI is enabled.
Which exact version of glide3? What compile flags did you give? Did it
spew any error messages before
Leif Delgass wrote:
On Fri, 5 Jul 2002, Jens Owen wrote:
[...]
The xc/config/cf/host.def in the DRI tree is setup to easily modified to
build a debuggable server. Attached is a copy of a modified host.def
file I used for debugging an i810 problem. You'll probably need to add
the
On Fri, 5 Jul 2002, Jens Owen wrote:
Leif Delgass wrote:
The backtrace from the static server was the same. BTW, this might help
others trying to debug with a dynamic server: I removed 'Load GLcore'
from my XF86Config, because I saw that it was being reloaded by the glx
module
There are files left over in the bsd DRM's driver subdirectories after
the merge to trunk. These got moved a directory above that (or to
shared/drm/kernel/), but the leftovers are getting in the way. I tried
to cvs rm and commit, but I got the following:
cvs server: failed to remove tag `HEAD'
21 matches
Mail list logo
