> As you have DRM now and as I'm not interested in wayland I won't discuss this, > but I guess it might be a good start for Geert's question what would be needed > to use it on dumb framebuffers. GMA500 is basically a 2D or dumb frame buffer setup but with a lot of rather complicated output and memory management required due to the hardware. With the latest changes to GEM (private objects) it's basically trivial to use the frame buffer management interfaces. > Yes, if you limit DRM to the functionality of the fb API I guess you could reach > the same stability level. But where can I do this? Where is a option to forbid > all acceleration or at least limit to the acceleration that can be done without > any risk? A driver can provide such module options as it wants. > That's a really difficult question. Determining the users is difficult and there > are people that use their hardware very long, for example we are about to get a > new driver for i740. For the framebuffer infrastructure I guess you have to at > least wait for my death. I doubt it'll be that long - but you are right it will take time and there isn't really any need to push or force it. These things take care of themselves and in time nobody will care about the old fb stuff, either because DRM covers it all or equally possibly because it doesn't support 3D holographic projection 8) Alan _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
