Re: Vertical retrace interrupts?

[Sven Luther <luther@dpt-info.u-strasbg.fr>]

On Fri, Jan 31, 2003 at 08:12:16PM +0100, Michel Dänzer wrote:
> On Fre, 2003-01-31 at 19:35, Antonino Daplas wrote:
> > On Fri, 2003-01-31 at 19:24, Michel Dänzer wrote:
> > > 
> > > 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?

Could it not be that the fbdev sort of minimally intialize the DRM when
it is not already active ? After all, the fbdev knows as much, if not
more, than the X driver about the graphic chips state, especially if the
X driver is using the fbdev.

Friendly,

Sven Luther


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com