Hi Dennis, On 7 Sep 2008, at 13:17, Dennis Schridde wrote: > On Sunday 07 September 2008 13:28:45 Kamaze wrote: >> Looks like a stuck situation, at least for the renderer. Does someone >> already have some ideas for the future? Different rendering parts to >> stay GMA compatible or breaking GMA support some day? > Can you get a bit more specific please? > What exactly is broken about rendering on Intel chips?
More the drivers; modern Intel chips are quite capable (the X3100 in my Macbook, and by extension the X3000 have reasonable support for modern OpenGL extensions). (Although performance is another issue.) The main issue is with their poor driver support on Linux and Windows. They claim to support framebuffer objects (but don't actually) — resulting in us having to workaround it ourself. No VBO support is another issue, even through it could be emulated should the card provide no real support for it. Most do not support fragment or vertex shaders. On the Windows side of things some of their chips have been shipping without support for age-old extensions such as GL_ARB_texture_rectangle, again things that are easy to emulate should there be no hardware support (just pad the texture with transparent pixels until it is power-of-two). The lack of FBO and VBO support is the main issue — down to nothing more than poor drivers. It is very hard to design a chip that does not support them [1] yet there is no driver support. This is poor, considering render-to-text has been part of DirectX (SetRenderTarget) since its inception and therefore has near perfect hardware support. VBOs, as I have already mentioned can be emulated if need be. The lack of FBO support is something of a thorn in betawidgets side — having buttons with things such as rotating models becomes quite difficult. Regards, Freddie. [1] http://lists.freedesktop.org/archives/xorg/2008-May/034844.html _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
