From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Re: waitforVBlank, how does this even work? Date: Fri, 04 Mar 2005 09:47:21 +1100 Message-ID: <1109890041.5610.230.camel@gaston> References: <9e473391050301215019081bce@mail.gmail.com> <1109806955.5610.129.camel@gaston> <1109816602.5610.153.camel@gaston> <20050303075559.GA7469@sci.fi> 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: Linux Fbdev development list Cc: Ville =?ISO-8859-1?Q?Syrj=E4l=E4?= , Jon Smirl , DRI developer's list On Thu, 2005-03-03 at 10:12 -0500, Vladimir Dergachev wrote: > >>>> 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. > > With one refinement - the DMA code would need to be a customer of IRQ > code.. No, again, DMA is what DRM is for, or you want to re-invent the whole architecture ? 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