http://bugs.xfree86.org/show_bug.cgi?id=271 ?
That seams like the one, I'm on an 8500 though. When I play quake3 it stopes, the
soundcard
loopes over it's dma like a broken record. Then quake3 exits(!0), don't know why I
hope the DRI
exited cause the card was hung. Why dose X not quit? When I
Quoting Michel Dänzer ([EMAIL PROTECTED]):
> On Wed, 2003-08-06 at 21:43, Denis Oliver Kropp wrote:
> >
> > When DRI has the graphics card lock for more than 100 ms, DirectFB
> > uses software rendering even if hardware rendering was available.
>
> I'm curious: How do you avoid conflicts betwee
Ian Romanick wrote:
Keith Whitwell wrote:
I'm happy to drop these once we have identified & implemented a
suitable replacement.
There are two ways to go on this. One way is to make a new
GLX_MESA_memory_allocate extension that just extends the existing
glXAllocateMemoryNV, glXFreeMemoryNV, a
Dark Nord wrote:
I have good configured xfree, with my CTX VL500 high sync monitor.
Normally I have on x resolution 1024x768x24 85hz an everything is ok.
But when I run games like UT & Tribes2 wchich hav their own renderers.
The refresh is 60 on 800x600x24/32 and on 1024x768x24/32 is wicked interl
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-06-08 21:16 ---
problems compiling the patch for 2.6.0-test2 kernel
CC drivers/char/agp/ali-agp.o
CC drivers/char/agp/ati-agp.o
drivers/char/agp/ati-agp.c: In function `ati_c
Hi all,
I tried to get flightgear running on my radeon mobility M7. The standard XFree
drivers lock up. The current dri binary modules corrupt big parts of the
screen at startup. The lockup is gone!
The neat new observation is that if the flightgear window is initially placed
to bottom right
On Mer, 2003-08-06 at 16:44, Marc-Christian Petersen wrote:
> > did you clean the tree up like in -ac's tree or did you take it as is
> > from some cvs repo ?
> nope, cvs. If Alan will be so kind to send me the fixes he made and I don't
> have to do the double-work, I'll integrate and test them up
On Mer, 2003-08-06 at 17:58, Marcelo Tosatti wrote:
> > It's a complete DRM-4.3 tree. He has to decide between an update of existing
> > 4.2 code or an addition of a new subdirectory drm-4.3 + proper config.in
> > entry.
>
> Does DRM 4.3 work with both XFree 4.2 and 4.3 ?
>
> I dont so, right?
On Tue, Aug 05, 2003 at 12:43:51AM +0200, Ove Kaaven wrote:
> I don't buy this argument. ValidateDevice doesn't do a lot of explaining
> either. The interface it presents is not hard to implement. I'm only
> asking for knowing at runtime that with the current environment, a
> fallback kicks in
On Tue, 05 Aug 2003 12:00:50 -0600
Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Ian Romanick wrote:
> > Ian Romanick wrote:
> >
> >> I'm also having second thoughts about allowing drivers to add function
> >> calls to the GLX dispatch table. This is a global table that has no
> >> way to identi
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-07-08 05:11 ---
For those of you who can't seem to get DRI working, follow these steps, I laid
it out step by step. The only part I didn't cover was patching the kernel, or
patching and bui
Ian Romanick wrote:
> Nathan Gray wrote:
>> Ian Romanick wrote:
>>>
>>>So, the example is drawing a wire-frame cube and clearing the screen as
>>>fast as it can on a single-buffered display? What do you think the odds
>>>are on a fast video card that the video refresh logic will just happen
>>>to
On Wed, 2003-08-06 at 07:25, Dieter Nützel wrote:
> The 2.4.22-rc1 radeon.o module is outdate of course.
> But the DRI CVS radeon.o module wouldn't load any longer.
>
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 941M
> agpgart: Detected AM
13 matches
Mail list logo
