Michel Dänzer написав(ла):
[...]
Is it normal that no interrupts happens from board?
or i need more initializing ioctl call to /dev/dri/0 to allow interrupts
from hardware?
This is probably due to the DRM_I830_SET_VBLANK_PIPE ioctl - the X
driver uses it to disable the vblank interrupts
Jesse Barnes написав(ла):
On Wednesday, August 27, 2008 1:20 pm Jesse Barnes wrote:
Here's a tested (on i915) patch for vblank-rework against drm-next with my
Could you give a hint how to apply this patch, what git repo should be
cloned for this patch?
I am very interesting in getting
http://bugzilla.kernel.org/show_bug.cgi?id=11465
Summary: Linux-2.6.27-rc5, drm errors in log
Product: Drivers
Version: 2.5
KernelVersion: 2.6.27-rc5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
http://bugzilla.kernel.org/show_bug.cgi?id=11465
--- Comment #2 from [EMAIL PROTECTED] 2008-08-30 14:45 ---
Handled-By : Dave Airlie [EMAIL PROTECTED]
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You
http://bugzilla.kernel.org/show_bug.cgi?id=11465
--- Comment #1 from [EMAIL PROTECTED] 2008-08-30 14:44 ---
Not-Handled-By : Arjan van de Ven [EMAIL PROTECTED]
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
Hi,
testing the r300-bufmgr has revealed that the driDestroyDrawable is never
called in very simple applications such as glxinfo or glxgears. This
obviously causes a number of memory leaks. Unfortunately, I don't really
understand that part of the code yet, but I have confirmed that the
