Re: [Patch] mach64 port to vblank rework

On Wednesday, October 31, 2007 3:12 Mathieu Bérard wrote: > +void mach64_disable_vblank(struct drm_device * dev, int crtc) > +{ > +   drm_mach64_private_t *dev_priv = dev->dev_private; > u32 status = MACH64_READ(MACH64_CRTC_INT_CNTL); >   > -   DRM_DEBUG("before install CRTC_INT_CTN

intel caching stuff..

Okay I've landed the drm and Mesa patches fot un-snooped cached mappings in the trees, the DDX code to use TTM for EXA is in the intel-batchbuffer branch of the intel repo.. This should resolve the gears slowdowns etc that were seen recently.. I've got a bit more testing to do, but I feel the

[Bug 12795] [915 TTM] server startup fails

http://bugs.freedesktop.org/show_bug.cgi?id=12795 [EMAIL PROTECTED] changed: What|Removed |Added Summary|since Merge remote branch |[915 TTM] server startup

[Bug 12968] Blender crashes on recent radeon dri drivers

http://bugs.freedesktop.org/show_bug.cgi?id=12968 --- Comment #5 from [EMAIL PROTECTED] 2007-10-31 15:23 PST --- (In reply to comment #4) > I can launch blender like this: > > LD_LIBRARY_PATH=/home/lenny/junk/Mesa-6.4.2/lib:$LD_LIBRARY_PATH > LIBGL_DRIVERS_PATH=/home/lenny/junk/Mesa-

[Patch] mach64 port to vblank rework

Hi, here is a patch that port the mach64 drm driver to vblank rework. It does not seems to cause any regression on my Rage Mobility P/M -- Mathieu Bérard diff --git a/linux-core/mach64_drv.c b/linux-core/mach64_drv.c index 9709934..16bc9ff 100644 --- a/linux-core/mach64_drv.c +++ b/linux-core/ma

[Bug 12968] Blender crashes on recent radeon dri drivers

http://bugs.freedesktop.org/show_bug.cgi?id=12968 --- Comment #4 from [EMAIL PROTECTED] 2007-10-31 15:11 PST --- I can launch blender like this: LD_LIBRARY_PATH=/home/lenny/junk/Mesa-6.4.2/lib:$LD_LIBRARY_PATH LIBGL_DRIVERS_PATH=/home/lenny/junk/Mesa-6.4.2/lib ./blender Problem solv

[Bug 12968] Blender crashes on recent radeon dri drivers

http://bugs.freedesktop.org/show_bug.cgi?id=12968 --- Comment #3 from [EMAIL PROTECTED] 2007-10-31 14:48 PST --- (In reply to comment #2) > Thank you for your reply, but this bug is not resolved. I checked out the > sources from GIT two days ago and I noticed that it only got worse. U

[Bug 12968] Blender crashes on recent radeon dri drivers

http://bugs.freedesktop.org/show_bug.cgi?id=12968 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

[Bug 12164] blender crash with DRI driver 7.0.1

http://bugs.freedesktop.org/show_bug.cgi?id=12164 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment

[Bug 12968] Blender crashes on recent radeon dri drivers

http://bugs.freedesktop.org/show_bug.cgi?id=12968 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: mapped cached memory and pre-fetching.

On 10/31/07, Thomas Hellström <[EMAIL PROTECTED]> wrote: > Dave Airlie wrote: > > On 10/31/07, Thomas Hellström <[EMAIL PROTECTED]> wrote: > > > >> Dave, > >> > >> When starting out with TTM i did look a little at AGP caching issues and > >> there was an issue with cached memory and speculative pre

[Bug 12164] blender crash with DRI driver 7.0.1

http://bugs.freedesktop.org/show_bug.cgi?id=12164 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #11816|text/x-patch|text/plain mime type|

[Bug 10090] Google Earth rendering trouble with Unichrome IGP

http://bugs.freedesktop.org/show_bug.cgi?id=10090 --- Comment #11 from [EMAIL PROTECTED] 2007-10-31 11:37 PST --- With current Mesa from Git the stability of 3D driver is a little bit better. Thanks for the latest commits. But this bug is still there with some visible changes. Here's

Re: Gtkradiant not working with radeon driver

Brian Paul wrote: > Roland Scheidegger wrote: >> git master still would have the same problem as far as I can see. >> The attached simple patch might fix the problem, if it really is what I >> think it is :-). >> I'm a bit unsure if DrawElements might have a similar problem, the same >> problem sho

Re: Gtkradiant not working with radeon driver

Roland Scheidegger wrote: > Jose Rodriguez wrote: >> On 30/10/2007, *Roland Scheidegger* <[EMAIL PROTECTED] >> > wrote: >> >> Hmm, so max_index is -1. Apparently gtkradiant has called drawArrays >> with a count of 0 (which is legal though pretty much a no-op), it s

Re: Gtkradiant not working with radeon driver

Jose Rodriguez wrote: > On 30/10/2007, *Roland Scheidegger* <[EMAIL PROTECTED] > > wrote: > > Hmm, so max_index is -1. Apparently gtkradiant has called drawArrays > with a count of 0 (which is legal though pretty much a no-op), it seems > we don't handle that

Re: Gtkradiant not working with radeon driver

On 10/31/07, Jose Rodriguez <[EMAIL PROTECTED]> wrote: > On 30/10/2007, Roland Scheidegger <[EMAIL PROTECTED]> wrote: > > Hmm, so max_index is -1. Apparently gtkradiant has called drawArrays > > with a count of 0 (which is legal though pretty much a no-op), it seems > > we don't handle that correct

Re: mapped cached memory and pre-fetching.

Dave Airlie wrote: > On 10/31/07, Thomas Hellström <[EMAIL PROTECTED]> wrote: > >> Dave, >> >> When starting out with TTM i did look a little at AGP caching issues and >> there was an issue with cached memory and speculative pre-fetching that >> may affect the mapped-cached memory, >> and that w

Re: Gtkradiant not working with radeon driver

On 30/10/2007, Roland Scheidegger <[EMAIL PROTECTED]> wrote: > > Hmm, so max_index is -1. Apparently gtkradiant has called drawArrays > with a count of 0 (which is legal though pretty much a no-op), it seems > we don't handle that correctly. (calculating start + count - 1 is a > problem there...).

Re: mapped cached memory and pre-fetching.

On 10/31/07, Thomas Hellström <[EMAIL PROTECTED]> wrote: > Dave, > > When starting out with TTM i did look a little at AGP caching issues and > there was an issue with cached memory and speculative pre-fetching that > may affect the mapped-cached memory, > and that we need to know about but perhaps

mapped cached memory and pre-fetching.

Dave, When starting out with TTM i did look a little at AGP caching issues and there was an issue with cached memory and speculative pre-fetching that may affect the mapped-cached memory, and that we need to know about but perhaps ignore. Suppose you bind a page to the AGP aperture, but don't ch