From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: waitforVBlank, how does this even work? Date: Thu, 03 Mar 2005 13:23:22 +1100 Message-ID: <1109816602.5610.153.camel@gaston> References: <9e473391050301215019081bce@mail.gmail.com> <1109806955.5610.129.camel@gaston> Reply-To: linux-fbdev-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit In-Reply-To: Sender: linux-fbdev-devel-admin@lists.sourceforge.net Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: Vladimir Dergachev Cc: Jon Smirl , fbdev , DRI developer's list 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...) 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