Re: waitforVBlank, how does this even work?

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

On Wed, 2005-03-02 at 09:30 +0200, Ville Syrjälä wrote:
> On Wed, Mar 02, 2005 at 06:10:14PM +1100, Benjamin Herrenschmidt wrote:
> > On Wed, 2005-03-02 at 00:50 -0500, Jon Smirl wrote:
> > > For the r128 driver both the fbdev and drm drivers have implemented
> > > waitforVBlank and they both play with the interrupt registers. I can
> > > only assume that no one has ever tried to use them at the same time.
> > > In the radeon case the DRM driver has implemented waitforVBlank and
> > > the fbdev driver has not.
> > > 
> > > This is a mess and it is yet another reason for merging DRM and fbdev
> > > into a sane, combined driver.
> > 
> > I'd say nobody ever used both :)
> 
> I (and others) have with mga. The easiest solution was to disable the irq 
> code in the drm. That was for running OpenGL on DirectFB btw.

I'd rather have disabled the IRQ code in the fbdev and added a
waitForVBlank in the DRM ...

Ben.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click