From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: waitforVBlank, how does this even work? Date: Fri, 04 Mar 2005 09:08:27 +1100 Message-ID: <1109887707.5679.214.camel@gaston> References: <9e473391050301215019081bce@mail.gmail.com> <1109806955.5610.129.camel@gaston> <1109816602.5610.153.camel@gaston> <20050303075559.GA7469@sci.fi> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit In-Reply-To: <20050303075559.GA7469@sci.fi> Sender: dri-devel-admin@lists.sourceforge.net Errors-To: dri-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: Ville =?ISO-8859-1?Q?Syrj=E4l=E4?= Cc: Vladimir Dergachev , Jon Smirl , fbdev , DRI developer's list > > 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. DMA handling is the main piece of what the DRM does, memory management is the missing part. No, what we really need is just what we said: merging fbdev & DRM and adding memory management. 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 --