[Intel-gfx] Interrupt handling across leave/entervt

Keith Packard keithp at keithp.com
Thu Jan 1 01:28:33 CET 2009


On Wed, 2008-12-31 at 13:56 -0800, Jesse Barnes wrote:

> Even though the drm_wait_vblank code takes a ref, the vblank interrupt doesn't 
> actually get re-enabled since when we get to drm_vblank_get dev-
> >vblank_enabled[crtc] is still set.  So something like the below also works.

This seems fine to me.

> But really, having the kernel try to keep its hands off of the hardware while 
> X is VT switched away is of arguable benefit, so I'd still rather just leave 
> things enabled across VT switches.

Another X server, not using DRM, may start and smash our status page.
The current VT switch requirement is that you return the HW back to its
previous state and leave it alone while you aren't active.

I sure can't wait to leave VT switching behind.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20081231/a6f406a8/attachment.sig>


More information about the Intel-gfx mailing list