Thread (16 messages) 16 messages, 5 authors, 2003-02-12

Re: Vertical retrace interrupts?

flat view

From: Michel Dänzer <hidden>
Date: 2003-01-31 19:12:22

On Fre, 2003-01-31 at 19:35, Antonino Daplas wrote:
On Fri, 2003-01-31 at 19:24, Michel Dänzer wrote:
quoted
You don't need X to use the DRM, just some privileged client to
initialize it.
You're right.  I just realized that since DRM already has an interrupt
handler, it is unwise for fbdev to install its own interrupt handler
too, as this will fatally lock up the machine when DRM and fbdev are
loaded simultaneously.

So, how about this?  Let fbdev have its own vblank ioctl, but for fbdev
drivers with a DRM counterpart, fbdev will just call the DRM
wait_vblank() and send_vbl_signals() functions.   Do you think this is
doable, I haven't examined the code thoroughly?  

The main goal is too avoid having 2 independent interrupt handlers for
one device.
A noble goal, but the framebuffer device would still need its own code
when the DRM isn't active, so I'm afraid there's no way around code
duplication, unless we could somehow factor out the common code for the
two to share?


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help