diff options
| author | Owain Ainsworth <oga@cvs.openbsd.org> | 2008-11-23 20:46:49 +0000 |
|---|---|---|
| committer | Owain Ainsworth <oga@cvs.openbsd.org> | 2008-11-23 20:46:49 +0000 |
| commit | 17ac785bb3a684774ebdad9381363f2883fec44a (patch) | |
| tree | 9e83e26cc13cf40543586011dc619d4106e18c9a /sys/dev/pci/drm/r128_drv.h | |
| parent | 00a60f9fe7c7c1784b2561115217114954996d0e (diff) | |
Move vblank data allocation to happening at attach, not at irq enable.
just put a vblank_pipes argument to the driver structure which tells us
how many to set up
this means that intel doesn't lose all vblank count on vtswitch (it
disables the interrupt there), i've heard of a few uvm_faults where this
happens as well as things just going wrong.
This was suggested by Keith Packard who provided a different diff for
drm.git.
Diffstat (limited to 'sys/dev/pci/drm/r128_drv.h')
| -rw-r--r-- | sys/dev/pci/drm/r128_drv.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/sys/dev/pci/drm/r128_drv.h b/sys/dev/pci/drm/r128_drv.h index 08df6195960..37d697e2930 100644 --- a/sys/dev/pci/drm/r128_drv.h +++ b/sys/dev/pci/drm/r128_drv.h @@ -166,7 +166,6 @@ extern void r128_disable_vblank(struct drm_device *dev, int crtc); extern u32 r128_get_vblank_counter(struct drm_device *dev, int crtc); extern irqreturn_t r128_driver_irq_handler(DRM_IRQ_ARGS); extern void r128_driver_irq_preinstall(struct drm_device * dev); -extern int r128_driver_irq_postinstall(struct drm_device * dev); extern void r128_driver_irq_uninstall(struct drm_device * dev); extern void r128_driver_lastclose(struct drm_device * dev); extern void r128_driver_preclose(struct drm_device * dev, |