On Friday, June 10, 2005 9:07 am, Jon Smirl wrote: > The Xegl model lets you pick where you get your drivers from. It just > runs on top of a driver stack providing the OpenGL/ES+EGL API. The > embedded systems I am aware of are ignoring mesa, drm, fbdev and and > building their own optimized OpenGL/ES stacks. The win is that the > same OpenGL/ES stack can be used with other operating systems.
Right, which is nice. But fundamentally, OpenGL|ES+EGL depends on a GL implementation (either sw or hw) and some sort of framebuffer control ability, right? On Linux, the GL aspect is provided by the current DRM/DRI layer, and the framebuffer control (modesetting, memory management?) is provided by the fb drivers, right? If that's the case, then I think the way you've tied together the drm and fb drivers make sense, since the most common setups in the brave new world of Xegl will require both. (Other configurations might be Xegl on top of some sort of equivalent BSD implementation or a proprietary stack, like nVidia's.) My point about KAA (or Shiny or whatever it ends up being) is that people, who for whatever reason don't want DRM/DRI (too big, too complex, or maybe they're just contrarians), can still just use the fb drivers by themselves along with whatever else they want on top. Jesse ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
