Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Michel Dänzer
On Mon, 2007-06-11 at 15:20 -0700, Jesse Barnes wrote: > On Monday, June 11, 2007 11:36:10 Keith Packard wrote: > > ick. just read the registers and return the value here. We should place > > wrap-detection in the core code by reporting the range of the register > > values; with the offset suggeste

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Michel Dänzer
On Mon, 2007-06-11 at 11:47 -0700, Keith Packard wrote: > On Mon, 2007-06-11 at 11:14 -0700, Ian Romanick wrote: > > > The problem is that a few of the GLX extensions (e.g., > > GLX_SGI_video_sync and GLX_OML_sync_control) allow applications to query > > the vblank counter directly. I don't know

Re: Bug#324560: libdrm2: Query on this DRM bug

2007-06-11 Thread Dave Airlie
Thanks for testing, I've just pushed the fix to Linus hopefully it gets in the next stable kernel.. Dave. Just tried it out and works perfectly kernel: [drm] Initialized drm 1.1.0 20060810 kernel: [drm] Initialized radeon 1.28.0 20060524 on minor 0 kernel: [drm] Setting GART location bas

Re: Bug#324560: libdrm2: Query on this DRM bug

2007-06-11 Thread Jason Cormie
Michel Dänzer wrote: > On Thu, 2007-06-07 at 08:58 +0100, Jason Cormie wrote: >> Michel Dänzer wrote: >>> So the X server is 32 bit? If so, there's probably indeed some kind of >>> 32/64 bit breakage somewhere, though unlikely related to the warnings in >>> the bug report you referenced. It looks l

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 7:32:34 Jesse Barnes wrote: > On Monday, June 11, 2007 7:13:04 Jesse Barnes wrote: > > On Monday, June 11, 2007 6:42:09 Keith Packard wrote: > > > On Mon, 2007-06-11 at 15:20 -0700, Jesse Barnes wrote: > > > > +static u32 last_vblank; /* protected by dev->vbl_lock */ > > >

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 7:13:04 Jesse Barnes wrote: > On Monday, June 11, 2007 6:42:09 Keith Packard wrote: > > On Mon, 2007-06-11 at 15:20 -0700, Jesse Barnes wrote: > > > +static u32 last_vblank; /* protected by dev->vbl_lock */ > > > > uh. per crtc? > > Oh, hm yeah. I guess it'll have to go in

Re: r300 texture rendering corruption

2007-06-11 Thread Oliver McFadden
Hi, I couldn't reproduce this with the latest Git of Mesa and DRM. Although R300 does have some lockup problems that get triggered after running UT2004 for a while... Try again using the latest Mesa and DRM from Git, and let me know if the texture corruption problem still exists. Thank you. On

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 6:42:09 Keith Packard wrote: > On Mon, 2007-06-11 at 15:20 -0700, Jesse Barnes wrote: > > +static u32 last_vblank; /* protected by dev->vbl_lock */ > > uh. per crtc? Oh, hm yeah. I guess it'll have to go in drm_device. > > + atomic_add(diff, &dev->vblank_count[crtc]);

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Keith Packard
On Mon, 2007-06-11 at 15:20 -0700, Jesse Barnes wrote: > +static u32 last_vblank; /* protected by dev->vbl_lock */ uh. per crtc? > + atomic_add(diff, &dev->vblank_count[crtc]); Ok, I think this is reasonable, although different from what I suggested. > + seq = atomic_read(&dev->vblank_

[git pull] drm fixes for 2.6.22-rc4

2007-06-11 Thread Dave Airlie
Hi Linus, Please pull the 'drm-patches' branch from the drm git tree, ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-patches It contains a fix for a radeon 32/64-bit issue along with hw support for some new Intel hw. Sorry for the lateness but I rely on AGP PCI IDS bein

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 11:36:10 Keith Packard wrote: > ick. just read the registers and return the value here. We should place > wrap-detection in the core code by reporting the range of the register > values; with the offset suggested above, that would result in a single > addition to convert fr

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Ville Syrjälä
On Mon, Jun 11, 2007 at 11:34:00AM -0700, Jesse Barnes wrote: > On Monday, June 11, 2007 11:14:45 Ian Romanick wrote: > > Jesse Barnes wrote: > > > We've had some IRC and off-list discussions about how to improve the > > > DRM's vblank code to be a bit more power friendly. The core requirement > >

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 11:36:10 Keith Packard wrote: > On Mon, 2007-06-11 at 10:59 -0700, Jesse Barnes wrote: > > The patch doesn't yet deal with two obvious cases (and probably more > > that I'm missing, it's untested yet): > > - the hardware counter resets on mode switch, we need to rebase >

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Keith Packard
On Mon, 2007-06-11 at 11:14 -0700, Ian Romanick wrote: > The problem is that a few of the GLX extensions (e.g., > GLX_SGI_video_sync and GLX_OML_sync_control) allow applications to query > the vblank counter directly. I don't know of other hardware that > maintains an actual counter. I know that

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Keith Packard
On Mon, 2007-06-11 at 10:59 -0700, Jesse Barnes wrote: > The patch doesn't yet deal with two obvious cases (and probably more > that I'm missing, it's untested yet): > - the hardware counter resets on mode switch, we need to rebase > the appropriate last_counter at that point so it's not tre

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
On Monday, June 11, 2007 11:14:45 Ian Romanick wrote: > Jesse Barnes wrote: > > We've had some IRC and off-list discussions about how to improve the > > DRM's vblank code to be a bit more power friendly. The core requirement > > is that we only enable vblank interrupts when a client is actually >

Re: [RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jesse Barnes wrote: > We've had some IRC and off-list discussions about how to improve the > DRM's vblank code to be a bit more power friendly. The core requirement > is that we only enable vblank interrupts when a client is actually waiting > for a v

[RFC] update DRM core vblank code to be more power friendly

2007-06-11 Thread Jesse Barnes
We've had some IRC and off-list discussions about how to improve the DRM's vblank code to be a bit more power friendly. The core requirement is that we only enable vblank interrupts when a client is actually waiting for a vblank event (be it a signal or a wakeup). This patch updates the DRM core,

[Bug 10978] Mesa 6.5.2 implementation error: User called no-op dispatch function

2007-06-11 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=10978 --- Comment #5 from [EMAIL PROTECTED] 2007-06-11 09:59 PST --- Does glxinfo say that GL_ARB_vertex/fragment_shader is supported? It won't for the R300 driver. I suspect that your game is trying to use the shading language without fir

[Bug 10978] Mesa 6.5.2 implementation error: User called no-op dispatch function

2007-06-11 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=10978 --- Comment #4 from [EMAIL PROTECTED] 2007-06-11 09:44 PST --- Here you go : Breakpoint 2, _mesa_problem (ctx=0x0, fmtString=0xb6c8a780 "User called no-op dispatch function (an unsupported extension function?)") at main/imports.c:9