http://bugs.freedesktop.org/show_bug.cgi?id=25847
--- Comment #4 from Tobias Jakobi <liquid.a...@gmx.net> 2010-01-02 04:44:37 PST --- Each OpenGL version has a list of mandatory features which must be supported by the GL (graphics library). Of course you could just advertise OpenGL 3.2 support for every hardware driver in Mesa (assuming that the software driver supports all OpenGL 3.2 features) and fall back to SW-rendering as soon as the application uses a features which the hardware doesn't natively support. However that's not how Mesa works. SW-rendering is slow, much slower than HW-accelerated rendering so each driver only advertises a feature-list which it can support (more or less) in hardware. Based on this feature-list the advertised OpenGL version is generated. If the hardware only supports all features that are needed for GL 1.4 but not all features for GL 2.0 -> then you only get version 1.4 advertised. !!! Only if all mandatory features for a given GL version are supported in hardware, then you get the version advertised by the driver. !!! There are of course exceptions, like the ARB_npot support on nvidia Geforce FX cards, but that's how it works in general and also for Mesa. Someone please correct me if I stated something wrong :) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
