Re: waitforVBlank, how does this even work?

["Ville Syrjälä" <syrjala@sci.fi>]

On Wed, Mar 02, 2005 at 10:01:00PM -0500, Vladimir Dergachev wrote:
> 
> 
> On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
> 
> >On Wed, 2005-03-02 at 20:03 -0500, Vladimir Dergachev wrote:
> >>
> >>On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
> >>
> >>>
> >>>>
> >>>>    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.
> >>>>
> >>>
> >>>Nope, I don't agree.
> >>
> >>With which part ? ;)
> >
> >On having a small stub module that does just IRQs ... I think the base
> >module should be the fbdev (mode setting etc...)
> 
> Oh, but I was not suggesting that. I just meant that interrupt handling 
> code is self-contained and can easily serve several consumers.

I'm with you here. And the same should IMHO hold for DMA handling. And for 
memory management of course.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-------------------------------------------------------
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
--