I don't quite understand how Mesa and device drivers play together... can someone explain this for me? I read the wiki (<a href="http://en.wikipedia.org/wiki/Mesa_(computer_graphics)" rel="nofollow">http://en.wikipedia.org/wiki/Mesa_(computer_graphics)</a>) and this (<a href="http://en.wikipedia.org/wiki/File:Linux_kernel_and_OpenGL_video_games.svg" rel="nofollow">http://en.wikipedia.org/wiki/File:Linux_kernel_and_OpenGL_vi...</a>) graphic makes it clear that Mesa is the implementation of the OpenGL specification... what I don't get is the relationship between drivers and Mesa. Why aren't the drivers the implementation of the OpenGL specification? Is pushing bits from the GPU to the screen the only thing that the drivers do?
If you were in the market for new hardware and wanted the purchase to support initiatives such as this--what would you buy?<p>I don't really game any more but like to support the ecosystem.
More good news for open source and Linux.<p>Valve is probably the most influential single entity in PC gaming, for them to embrace open-source to this degree is massive...
You would think with Steam banking it big with the Steambox that they would want people working on these sorts of projects, as it's not only Steam that wins big (having a FOSS OS to run their steam box on), but everyone else.
I'm not conviced this will help that much for Intel GPUs. Developers from Intel have been optimizing shader compilers specifically for Dota 2 for some time without much impact on performance.<p>Dota 2 is probably memory bandwidth limited on Intel/Linux/OpenGL and that is likely the case for other games too.<p>So maybe modifying the OpenGL part of the game engine a bit to take memory bandwidth constraints of Intel GPUs into account would help more.<p>When I was looking into the issue of Intel GPU peformance on Linux many months ago there were no tools to profile memory bandwidth bottlenecks.
Presently each SCM (Subsea Control Module) uses a specific protocol to communicate with the topside system. The topside system often polls the SCM for data. In the case of RRC there are currently three different types of SCM and these use the following protocols: 2000, 3000 and 1024. how we can program a common driver interface and that will include the three protocols and the top side don't three package to control the three different subsea module ?????
Thought this was going to be an announcement about <a href="http://www.blackmesasource.com" rel="nofollow">http://www.blackmesasource.com</a> or HL3
At first reading, I thought it was about Black Mesa [1], the Half-Life (first Valve game) remake made by the community.<p>[1] <a href="http://www.blackmesasource.com/" rel="nofollow">http://www.blackmesasource.com/</a>