W dniu 1 grudnia 2009 08:33 użytkownik Michel Dänzer <mic...@daenzer.net> napisał: > On Tue, 2009-12-01 at 08:03 +0100, Rafał Miłecki wrote: >> 2009/12/1 Alex Deucher <alexdeuc...@gmail.com>: >> > On Mon, Nov 30, 2009 at 2:02 PM, Alex Deucher <alexdeuc...@gmail.com> >> > wrote: >> >> This enables the use of interrupts on r6xx/r7xx hardware. Interrupts >> >> are implemented via a ring buffer. The GPU adds interrupts vectors to >> >> the ring and the host reads them off in the interrupt handler. The >> >> interrupt controller requires firmware like the CP. This firmware >> >> must be installed and accessible to the firmware loader for interrupts >> >> to function. >> > >> > Updated patch. fixes some minor issues in the previous one. >> >> Same issue with updated one. modprobed radeon, not a one VBLANK. >> Started X and KDE, got first VBLANK on 48sec and received them cyclic >> until 87sec. Then it just stopped. > > Note that vblank interrupts are only supposed to be occur while > userspace is waiting for vblank events.
Could you tell me how can I wait for vblank from kernel space, please? I see there is drm_wait_vblank but this is not yet exported. I tried export this and use this with _DRM_VBLANK_ABSOLUTE so I hit > DRM_WAIT_ON(ret, dev->vbl_queue[crtc], 3 * DRM_HZ, but that was busy waiting I think, as my desktop was almost not usable. Also Alex believe I should *not* use drm_* for syncing my kernel module code with vblank. -- Rafał ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
