On Fri, 7 Jan 2011 09:16:51 +1000 Dave Airlie <airlied@xxxxxxxxx> wrote: > From: Dave Airlie <airlied@xxxxxxxxxx> > > This is just an idea that might or might not be a good idea, > it basically adds two ioctls to create a dumb and map a dumb buffer > suitable for scanout. The handle can be passed to the KMS ioctls to create > a framebuffer. > > It looks to me like it would be useful in the following cases: > a) in development drivers - we can always provide a shadowfb fallback. > b) libkms users - we can clean up libkms a lot and avoid linking > to libdrm_*. > c) plymouth via libkms is a lot easier. > > Userspace bits would be just calls + mmaps. We could probably > mark these handles somehow as not being suitable for acceleartion > so as top stop people who are dumber than dumb. Would extracting libwfb from the server and providing it as a standalone fb access API from the server also fill these needs? It would be a bigger API, but presumably would allow us to share fbs between early boot and subsequent, accelerated usage. We'd still need to settle on the basic allocation API, but we seem to manage that on the server side... -- Jesse Barnes, Intel Open Source Technology Center _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
