<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - intel hd4600 missing features" href="https://bugs.freedesktop.org/show_bug.cgi?id=74935#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - intel hd4600 missing features" href="https://bugs.freedesktop.org/show_bug.cgi?id=74935">bug 74935</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>The OpenGL API split into two "profiles" starting with 3.1/3.2: - The "compatibility" / legacy profile, which is backwards compatible all the way to GL 1.x. - The "core" profile, which drops a lot of deprecated functionality, allowing new features to implemented cleanly and more optimally. Since the "core" profile is not backwards compatible, applications have to specifically ask for it. Otherwise, we give them the highest versioned compatibility/legacy context we support, which is 3.0. Note that Apple takes the same approach as Mesa: on OS X, you can ask for an OpenGL 2.1 context, or an OpenGL 3.2+ core profile context. So, authors of OpenGL applications already have to cope with this. In general, older engines work with the legacy mode, and new engines being written are targeting the core profile.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>