Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Graphics Open Source Upgrades

Open-Source Intel Mesa Driver Now Supports OpenGL 3.2 35

An anonymous reader writes "Mesa and its open-source Intel graphics driver now are in compliance with the OpenGL 3.2 specification (PDF). It took four years for Mesa to get up to GL 3.2 / GLSL 1.50 compliance, and support for the other Mesa drivers isn't too far behind, but they're still years behind in supporting OpenGL 4. Supporting a major new OpenGL API has resulted in Mesa 10.0 being called the next release. It has many other features, like performance improvements and new Gallium3D features. OpenGL 3.3 support might also be completed prior to the Mesa 10.0 release in November."
This discussion has been archived. No new comments can be posted.

Open-Source Intel Mesa Driver Now Supports OpenGL 3.2

Comments Filter:
  • This is truly a great day for Linux gaming.

  • Isn't Mesa software rendering? I've never found it to be anything but abysmal performance. Why does anyone use it?

    • by paskie ( 539112 )

      Nope. Mesa is a generic OpenGL API implementation that can use multiple backends - either software rendering or Gallium / DRI.

    • by Anonymous Coward

      Mesa is the graphics API implementation that can used for both software and hardware-accelerated rendering.

    • Re:Cool, but why? (Score:5, Informative)

      by timeOday ( 582209 ) on Friday October 11, 2013 @04:06PM (#45104757)
      I had thought the same, but from the first 3 sentences of "Mesa Introduction" on their homepage, mesa3d.org:

      Mesa is an open-source implementation of the OpenGL specification - a system for rendering interactive 3D graphics.

      A variety of device drivers allows Mesa to be used in many different environments ranging from software emulation to complete hardware acceleration for modern GPUs.

      Mesa ties into several other open-source projects: the Direct Rendering Infrastructure and X.org to provide OpenGL support to users of X on Linux, FreeBSD and other operating systems.

      and later on the page...

      Mesa is the OpenGL implementation for several types of hardware made by Intel, AMD and NVIDIA, plus the VMware virtual GPU. There's also several software-based renderers

    • by Kjella ( 173770 )

      Isn't Mesa software rendering? I've never found it to be anything but abysmal performance. Why does anyone use it?

      Mesa is many things, among them a huge graphics library to support the OpenGL API, a reference software rendering driver and a bunch of hardware accelerated drivers. The only reason to use the software rendering is to test accelerated drivers or because you don't have a choice and in the past you didn't really have a lot of choice. Today AMD and Intel has official open drivers, for nVidia there's the community built Nouveau that all have good hardware acceleration support, so it's pretty hard to find a grap

    • Re:Cool, but why? (Score:5, Informative)

      by Anonymous Coward on Friday October 11, 2013 @04:22PM (#45104891)

      It is a pretty complicated setup for the uninitiated, but the basics are this:

      Mesa was originally just a reference software implementation of OpenGL. People started making graphics drivers that started accelerating parts of the graphics rendering code. These drivers grew quite large and are considered "classic drivers". They are mostly just big monolithic blobs that accelerate whatever they please. The intel driver is one of the only classic drivers remaining.

      People wanted something a bit more flexible and easier to extend, so gallium3d was devised. Shaders are compiled into an intermediate language called TGSI, and then passed to the gallium3d drivers to be converted into command streams/assembly that will run on the video card. This system is a bit like a generic interface to the card's capabilities, and can in theory be run independently of OpenGL. Nouveau and radeon both use gallium3d drivers instead of the classic driver model.

      All of the modern 3d accelerated drivers also make use of the DRI interface, which is an interface to the linux drivers that allows them to pass draw commands directly to the kernel's drm driver. There are also state trackers, which help generate TGSI for the gallium drivers. These exist for things like dri, gles, opencl, vdpau and help make sharing functionality between the various gallium3d drivers easier.

      There are probably a few things wrong in here so don't take it as scripture, but it should give the overall picture of how things work. If anyone notices anything wrong please point it out.

Some people manage by the book, even though they don't know who wrote the book or even what book.

Working...