Re: Re: waitforVBlank, how does this even work?

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

On Wed, 2005-03-02 at 17:29 +0000, James Simmons wrote:
> > Hi Jon,
> > 
> >     What about isolating interrupt-handling code into a small driver ?
> > Something simple to respond to interrupts and call all handlers with a 
> > certain mask.
> > 
> >     This would be useful not only for drm and fbdev but also for km 
> > (v4l capture module) and stereo-glasses code.
> 
> Ultimatly this is the goal. That is what the struct xxx_par is for in 
> struct fb_info. It is the core driver private data that can be shared by 
> everyone. Ben would you mind if I reworked your code to have this "core".
> It will take me some time but I can have it working. I need to do some 
> fixes for multiple monitor handling anyways.

Wait, wait ... there is already Jon working on the driver, and I plan to
include part of his recent work along with some initial dual head
support soon, let's avoid having too many people working at the same
time on it.

Also, with the merge DRM/fbdev, this will become a non-issue, wether the
ioctl comes from DRM or fbdev, we'll be able to do the right thing.

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_id=6595&alloc_id=14396&op=click