Talk:Mesa (computer graphics)

message: Perhaps some information on where its currently used? (IE practical applications of Mesa that exist)
: Hmm, maybe we should add a section called Adoption. But it would be either very short: "everywhere" and a hell of a long list. User:ScotXWt@lk 20:51, 7 June 2014 (UTC)
thread_title: Where is it used?

message: gNewSense had to remove it, Debian also has a running discussion on it: [], [], [], [] bkil (talk) 16:28, 5 August 2008 (UTC)
replies: text: The worst part of it all is what you just said: this problem has been known for more than 8 years now! If you gave a look at the links, including the final words up to 2008 (and those referenced from there...), you would understand the full issue, and that it has been on the to-do lists for some time. I repeat: gNewSense has removed all of its 3D support just because of this 'minor' issue. Some of the 'infected' source had spread around Xorg (that's why it's been initially filed at the xfree86 package), but gNewSense has more or less successfully isolated the offending parts. GNU GPL software can only be combined with files using so called GNU compatible licenses, which some of the Mesa sources fail to adhere. To my limited legal understandig, this means that Mesa can not be free software. It could be called open source, if the remaining parts did not use the GPL, but to this point, I'm not sure if the package is legal at all! If you feel the issue has been resolved, please post links to the resolution here, I'm putting the fact tag back until then, if you don't mind. Thank you for your feedback, do keep us posted. bkil (talk) 18:12, 22 August 2008 (UTC)
replies: text: Whatever I said, minus the GPL part. So it might end up being a validly licensed open source (but not free software) package. Sorry, but I'm too tired to sort that out at the moment... bkil (talk) 18:29, 22 August 2008 (UTC)

text: Splendid! Thank you for the information Potatobackwards. :) I can't wait to see 3D in gNewSense again! ;) They say full negotiations with later contributors to the licensed parts could take a month or so. Maybe we could copy the link you've given to the main article, or even one or more of these: , , ... Or perhaps we could wait until things are settled out. bkil (talk) 17:25, 8 October 2008 (UTC)
thread_title:  Mesa is *not* free software 

message: Is there a reason the title isn't "Mesa 3D"? —danhash (talk) 13:31, 28 September 2011 (UTC)
replies: text: +1 Doors5678 (talk) 17:10, 13 April 2012 (UTC)
replies: text:  It really should be Mesa 3D ScotXW (talk) 11:10, 8 September 2013 (UTC)

text: Yes, the project's name is "Mesa". For some reason, the project's domain name is mesa3d.org, however. I imagine this is due to mesa.org's unavailability. --Chealer (talk) 18:18, 6 October 2013 (UTC)
thread_title:  Title 

message: Greetings,
This is my first post to any "talk" page so be kind (even if maybe it seems that I am not).
I just felt compelled to note that the final paragraph in the "History" segment of this article really ought to be rewritten by someone who speaks English.  OK, sorry.  I don't mean to be a wise-ass.  It's just that the verbiage in that paragraph, particularly the first sentence of the paragraph, definitely needs work.  I started to try to just simply clean up the English usage in that paragraph myself, but then I realized that I could not effectively do so for the simple reasons that (a) I have little or no knowledge of the subject matter in the first place and also (b) I can't even totally puzzle out what exactly the original author was even _trying_ to say in the paragraph in question.  (I can't paraphrase or re-write something that's not even entirely comprehensible in the first place.)
So I guess that the original author is/was trying to say that Mesa is composed of pieces (which he calls "components" in one place and "modules" elsewhere in the same paragraph) and that the interfaces between the pieces are generally stable, and that this fact in turn allows the separate pieces to evolve on their own while still inter-operating with the whole.
Basically, it appears that this entire paragraph is only there so that the author could say (in effect, and three separate times in three separate and different ways) that the parts of Mesa can and have evolved separately.
Separate sub-components and stable internal interfaces are not exactly novel concepts, so I'm kind of left wondering why this aspect of Mesa is even worthy of special mention, let alone why it might best appear in a "History" section, of all places.
As I say, I would be happy to take a whack at revising this paragraph myself, but I thought that I should post here first and see what people who know the subject matter better than I do... which is to say everybody... might have to say.
Rfg-ronbaby (talk) 20:53, 21 October 2012 (UTC)
thread_title:  Bad English, fuzzy meaning 

message: : While the fundraising-campains of Mozilla have been very successful, there are only 3.5 people working full-time on the Linux ALSA audio drivers.
I don't think the above is relevant to this article given that ALSA is for sound drivers and nothing to do with graphics.
86.186.132.36 (talk) 11:34, 29 October 2013 (UTC)
thread_title:  What does ALSA have to do with Mesa? 

message: On the onset of Mesa 11.0's release, this article needs to accommodate more info about Mesa 11.0. Whether it is something unclear on the talk about Mesa or this article, but I think a section about 11.0 should be added, as well as clarification that later versions of OpenGL won't affect all drivers. Vormeph 20:41, 26 August 2015 (UTC)
replies: text: I agree.  The third paragraph under Implementations of rendering APIs could be expanded.  It would be too exhaustive to mention all drivers though and it does not belong in the corresponding table.  Now it seems to imply that other drivers actually support OpenGL 4.2. -- Lightkey (talk) 21:13, 10 September 2015 (UTC)
thread_title:  Regarding Mesa 11.0 

message: New Software Rasterizer for Cluster with much more Performance.
See http://openswr.org and http://openswr.org/perf.html and actual  https://mesamatrix.net For more. — Preceding unsigned comment added by 91.67.31.234 (talk) 11:06, 24 May 2016 (UTC)
thread_title:  OpenSWR 

message: http://mesa3d.org/relnotes/13.0.1.html  — Preceding unsigned comment added by 95.90.229.157 (talk) 19:12, 15 November 2016 (UTC)
thread_title:  New Version 13.0.1 

message: Today available 13.0.2  — Preceding unsigned comment added by 95.90.229.183 (talk) 19:10, 28 November 2016 (UTC)
thread_title:  New Version 13.0.2 available at git 

message: 13.0.4 available  — Preceding unsigned comment added by 2A02:810B:C53F:B9E8:85D9:2504:AD1C:1E67 (talk) 15:43, 1 February 2017 (UTC)
thread_title:  13.0.4 available 

message: see
http://www.phoronix.com/scan.php?page=article&item=mesa-172-features&num=1  — Preceding unsigned comment added by 2A02:810B:C53F:B9E8:256F:74C8:49C0:C961 (talk) 23:19, 29 August 2017 (UTC)
thread_title:  mesa 17.2 

message: Hello fellow Wikipedians,
I have just modified 3 external links on Mesa (computer graphics). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://archive.is/20130416120341/http://www.x.org/wiki/DRI2 to http://www.x.org/wiki/DRI2
*Added  tag to http://www.tungstengraphics.com/technologies/gallium3d.html
*Added archive https://web.archive.org/web/20080704122122/http://wiki.x.org/wiki/DRI2 to http://wiki.x.org/wiki/DRI2
*Added archive https://web.archive.org/web/20080731072038/http://www.bitblit.org/gsoc/g3dvl/ to http://www.bitblit.org/gsoc/g3dvl/
*Added  tag to http://stecchino.blip.tv/file/1181861/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 11:16, 26 January 2018 (UTC)
thread_title:  External links modified (January 2018) 

message: See 
https://www.x.org/wiki/Events/XDC2017/nasri_mesa.pdf  — Preceding unsigned comment added by 2A02:810B:C53F:B9E8:D54B:B274:9D38:538C (talk) 18:47, 21 March 2018 (UTC)
thread_title:  Intel Mesa i965 History on xdc2017 Teamleader Nasri 

message: End of Bugfix in 17.3 actual extended to 17.3.9 in calendar Of project  — Preceding unsigned comment added by 95.90.228.26 (talk) 10:45, 23 March 2018 (UTC)
thread_title:  End of Bugfix in 17.3 extended to 17.3.9 in calendar 

message: See Text in 18.0.0 and or 17.0.0 or 17.0.1  — Preceding unsigned comment added by 2A02:810B:C53F:B9E8:C0BA:6AEB:67C7:BC7D (talk) 17:09, 4 April 2018 (UTC)
thread_title:  Stable Release is 1*.0.1 and Last preview is 1*.0.0 

message: Table should be 
Hardware firm like Intel 
Line like Haswell
Version Mesa like 18.0
Supported Version OpenGL here 4.5
Same for OpenGL ES and Vulkan and the other api.
1st Source of info about this is
https://people.freedesktop.org/~imirkin/glxinfo/  — Preceding unsigned comment added by 2A02:810B:C53F:B9E8:741C:E0A5:AD9C:3E92 (talk) 10:55, 13 April 2018 (UTC)
thread_title:  New Table of support of different Hardware in Mesa with latest Version possible 

message: https://en.wikipedia.org/w/index.php?title=Mesa_%28computer_graphics%29&diff=prev&oldid=1013404435
It seems to either have some bad typos or be written by someone who mostly speaks german.  — Preceding unsigned comment added by 66.27.77.211 (talk) 09:27, 17 January 2022 (UTC)
thread_title:  Is this edit intentional? 

message: een looking for a good place to ocument issues within a server whether it be long running source code, or improper use of Apache licensing for wearbles and near by devices. Frm blink ccessibility issues t improper data removal and manpulation. Idealbrocolli (talk) 23:58, 11 November 2022 (UTC)
thread_title:  Updating Some Very wrong code that is flowing though a server environment. 

message: See
https://www.phoronix.com/news/OpenGL-4.5-D3D12-Mesa
and mesamatrix. 2A02:6D40:34BF:4001:3055:5E84:CA88:68EB (talk) 12:25, 15 November 2023 (UTC)
thread_title:  Microsoft Dozen supports OpenGL 4.5 in Mesa 24.0 

message: The infobox field for preview release screwed up. No idea on how to fix. Any help is welcome. NasssaNsertalk 14:26, 30 November 2023 (UTC)
replies: text: Fixed by setting preferred rank to the latest RC. NasssaNsertalk 11:24, 1 December 2023 (UTC)
thread_title:  Preview release infobox field screwed up