On Wed, Mar 26, 2008 at 1:50 PM, Tom Cooksey <[EMAIL PROTECTED]> wrote: ... > I guess what I was thinking about was a single API which can be used on > 3D-less > (or legacy, if you want) hardware and on modern hardware. If the graphics > hardware > is a simple pointer to a main-memory buffer which is scanned out to the > display, then > your right, you might as well just use user-space shared memory, as we > currently do. > A new API would only be useful for devices with video memory and a hardware > blitter. > There are still new devices coming out with this kind of hardware, the > Marvel PXA3x0 > and Freescale i.MX27 for example spring to mind.
I agree with you that it probably doesn't make sense to use gallium/mesa on everything everywhere. There are still small devices or early boot scenarios (you mention initramfs) where gallium isn't appropriate. However, there is no need to put this a 2D engine into the kernel. What the drm ttm gives us is a nice abstraction for memory management and command buffer submission, and drm modesetting builds on this to let the kernel set a graphics mode. And that's all that we need in the kernel. Building a small userspace library on top of this to accelerate blits and fills should be pretty easy. cheers, Kristian ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
