[Mesa-dev] Help for a beginner

Hi all! I'm an experienced programmer, but I've never touched the mesa code. I desperately want to help, but for that, I need a mentor to teach me the basics about the project, the good practices and eventually drive me through the bugs and features. I'd be glad to begin with a simple, but long

Re: [Mesa-dev] Help for a beginner

Hi Tom, hi Christian, 2011/9/26 Tom Stellard tstel...@gmail.com Glad you're interested. We can always use more help. I think the best way to get started is to find something to work on that is interesting to you. So, I have two questions: What hardware do you have, and why do you want to

Re: [Mesa-dev] Help for a beginner

Great !! I'll read this right away! Thanks! 2011/9/26 Benjamin Bellec b.bel...@gmail.com: Le 26/09/2011 20:25, Romain Failliot a écrit : At first, it would be questions like how to run my own compiled mesa drivers? I should handle getting the code, compiling it and editing it. Things I've

Re: [Mesa-dev] Help for a beginner

Hi Eric, I tried to email you to have more information about the VS5 task (dead code elimination), but your email address on your page (http://dri.freedesktop.org/wiki/EricAnholt) was wrong :/ I'd definitely recommend working on a texturing format extension for your hardware as a great way to

Re: [Mesa-dev] Help for a beginner

2011/10/6 Heath Feather hfeat...@tabula.com: Try seeing which libraries you're picking up , here my LD_LIBRARY_PATH was set to /home/hfeather/work/downloads/Mesa-7.0.1/lib64/ Thanks! Actually I don't have a lib64 directory, but just lib. What did you do to build for 64 bits? BTW I've got F15

Re: [Mesa-dev] Help for a beginner

2011/10/6 Ian Romanick i...@freedesktop.org: You will have to *completely* uninstall the NVIDIA closed-source driver in order to use the Mesa driver.  NVIDIA installs their own kernel module and their own libGL, so it is impossible for both to live on the same system. Well, last time I checked

Re: [Mesa-dev] Help for a beginner

For my problem with the nouveau driver burning up my card, I'll take the simplest solution: get an ATI card (nVidia should have opened up their specs!). 2011/9/27 Eric Anholt e...@anholt.net: I'd definitely recommend working on a texturing format extension for your hardware as a great way to

[Mesa-dev] The GL3.txt format

Hi! I made a PHP script to have a better representation of the OpenGL compliance of Mesa: http://creak.foolstep.com/mesamatrix/ But I'm not sure about the signification of some lines. When there is a DONE, with no parenthesis after, does it means it's done for all the drivers? And when there is

Re: [Mesa-dev] The GL3.txt format

Cool. You may also be interested in http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html which takes a more pragmatic approach of just using whatever is reported by glxinfo for various hardware for released mesa versions. That is impressive! Seems reasonable. You're just talking

Re: [Mesa-dev] The GL3.txt format

mar...@gmail.com: It's not correct. For example, transform feedback shouldn't be listed for r300. Marek On Sat, Aug 23, 2014 at 11:59 PM, Romain Failliot romain.faill...@foolstep.com wrote: Hi! I made a PHP script to have a better representation of the OpenGL compliance of Mesa

Re: [Mesa-dev] The GL3.txt format

...@vmware.com: Am 25.08.2014 07:56, schrieb Kenneth Graunke: On Monday, August 25, 2014 12:05:07 AM Romain Failliot wrote: Some folks helped me and a lot of detection bug have been fixed! I have a question though (for my own culture): what's with the swrast, the softpipe and the llvmpipe

Re: [Mesa-dev] The GL3.txt format

Hi guys! Little recap on my project. I don't know if've been there recently but there has been some nice changes (thanks for the llvmpipe and softpipe cleanup by the way). http://creak.foolstep.com/mesamatrix/ I'm wondering if something could be done for the r300 status. I think it will

Re: [Mesa-dev] The GL3.txt format

:57 PM, Romain Failliot romain.faill...@foolstep.com wrote: Hi guys! Little recap on my project. I don't know if've been there recently but there has been some nice changes (thanks for the llvmpipe and softpipe cleanup by the way). http://creak.foolstep.com/mesamatrix/ I'm wondering

Re: [Mesa-dev] feature request for mesamatrix.net

I appreciate the work you've done to make the GL3.txt file much more readable. To improve it even more I would like to be able to click on the extensions names and see the whole text of the extension from the registry on opengl.org. I think it would help to understand why something isn't

Re: [Mesa-dev] [PATCH] Set llvmpipe and softpipe note only for MSAA.

02.11.2014 um 18:35 schrieb Romain Failliot: Hi! Sorry if I'm doing this wrong, first time here. I've tried git send-mail, but I don't have an SMTP server so it wasn't working. Here is the simple commit (and the patch attached): Set llvmpipe and softpipe note only for MSAA. Right now

Re: [Mesa-dev] [PATCH] Set llvmpipe and softpipe note only for MSAA.

Cool! Thanks a lot! Le 27 nov. 2014 12:05, Roland Scheidegger srol...@vmware.com a écrit : Sorry for that. Someone (== me) didn't realize he needs to push it :-). Done that now. Roland Am 27.11.2014 um 01:53 schrieb Romain Failliot: Hi! I'm not familiar with the patch and merge

[Mesa-dev] List of unsupported extensions per driver

Hi! First, I wanted to thank you for the incredible work you've done to achieve OpenGL 4.1. The number of visitors exploded on mesamatrix, while the average was around 100 visits per day, I had more than 2500 visits just for the day of the news! This simple fact shows how much this news was

Re: [Mesa-dev] List of unsupported extensions per driver

in myself, for radeon, I think GlennK provided it. I asked the intel guys a while back, but they didn't seem interested in providing the info for their HW (and I didn't push for it). Hope this helps, -ilia On Wed, Jul 29, 2015 at 12:35 AM, Romain Failliot romain.faill...@foolstep.com

Re: [Mesa-dev] List of unsupported extensions per driver

Hi! I'm diving into the unsupported extensions list and I'm wondering how is it possible that GL_ARB_gpu_shader5 is unsupported for R600, but some of the "sub-extensions" like "Dynamically uniform sampler array indices" are supported nonetheless. That makes me wonder if "not done"

Re: [Mesa-dev] List of unsupported extensions per driver

t; > Marek > > On Tue, Sep 29, 2015 at 7:32 AM, Romain Failliot > <romain.faill...@foolstep.com> wrote: > > Hi! > > > > I'm diving into the unsupported extensions list and I'm wondering how is > it > > possible that GL_ARB_gpu_shader5 is unsupported for R6

Re: [Mesa-dev] List of unsupported extensions per driver

2015-10-01 3:33 GMT+02:00 Ian Romanick : > The two lines that just have () are only supported on i965, nvc0, and > radeonsi. It's not really that clear. > Yep, this part I understood, once you understand it's hierarchical, everything becomes clearer ;) Also, a guy on

Re: [Mesa-dev] List of unsupported extensions per driver

Freeman <albertwdfree...@gmail.com>: > On 29 September 2015 at 14:48, Romain Failliot > <romain.faill...@foolstep.com> wrote: > > What I don't understand is that all the lines starting with a "-" seems > to > > be part of the GL_ARB_gpu_sha

Re: [Mesa-dev] List of unsupported extensions per driver

Le 29 sept. 2015 7:22 PM, "Ilia Mirkin" a écrit : > R600/R700 will never support ARB_gpu_shader5. Evergreen and NI > families (also driven by the r600g driver) will gain support for it in > due time. Aaaah I think I understand my misunderstanding: the R600 drivers (in

[Mesa-dev] [PATCH] Fix warnings.

Can now compile with -Werror. Fixed -Wunused-variable, -Wunused-but-set-variable, -Wmaybe-uninitialized and -Wunused-function. To prevent warnings for variables only used in asserts, I void them right after the call to assert(). --- src/compiler/spirv/vtn_variables.c | 1 +

[Mesa-dev] [PATCH v2 2/4] docs: Realign the "Status" column.

The "Status" column was misaligned in some GL sections. This is a lot of diffs, but it's only spaces in the end. --- docs/GL3.txt | 278 +-- 1 file changed, 139 insertions(+), 139 deletions(-) diff --git a/docs/GL3.txt b/docs/GL3.txt index

[Mesa-dev] [PATCH v2 3/4] docs: Renormalize some extensions.

This fixes some exceptions I have to deal with in mesamatrix.net. The extensions GL_ARB_texture_buffer_object had a comment between "DONE" and the brackets. And the extension GL_KHR_robustness (in GL 4.5 and GLES 3.1) was using "90% done" instead of "in progress". The "90% done" is still here

[Mesa-dev] [PATCH v2 1/4] docs: howto to read and edit GL3.txt

Added a small guide on how to read and edit GL3.txt. I think this would help as much the devs as the users reading this file. --- docs/GL3.txt | 25 - 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/docs/GL3.txt b/docs/GL3.txt index ee7faca..1ed5c1a 100644

[Mesa-dev] [PATCH v2 4/4] docs: Renormalize older extensions.

For older extensions, there is an explanation first and the extension name in brackets, like that: Clamping controls (GL_ARB_color_buffer_float) I inverted that so we have the extension first and then the explanation in brackets, like that: GL_ARB_color_buffer_float (Clamping controls) It

Re: [Mesa-dev] [PATCH v2 3/4] docs: Renormalize some extensions.

I sent a v2 of the patches with your proposition Nicolai. I think I don't have the rights to push patches, so it would be great if you could do it. 2016-03-15 16:14 GMT-04:00 Romain Failliot <romain.faill...@foolstep.com>: > This fixes some exceptions I have to deal with in mesam

[Mesa-dev] Small changes in GL3.txt

Hi! With the recent commits, I'm having some trouble parsing the GL3.txt text file for mesamatrix.net. With these set of 4 patches, I'm proposing to rationalize a little bit this file. The content is exactly the same. (Note: I'm not really used to propose patches, so if this format is wrong,

Re: [Mesa-dev] [PATCH 3/4] docs: Renormalize some extensions.

Hmm... I thought that was what it meant. I can add a new status like "paused" for instance. 2016-03-14 22:40 GMT-04:00 Ilia Mirkin <imir...@alum.mit.edu>: > "In progress" would seem to imply someone is working on it, which, AFAIK, is > not the case. > > On

Re: [Mesa-dev] Small changes in GL3.txt

Thanks for the explanations, I'll resend these patch the right way. 2016-03-14 10:01 GMT-04:00 Nicolai Hähnle <nhaeh...@gmail.com>: > Hi Romain, > > On 13.03.2016 16:50, Romain Failliot wrote: >> >> Hi! >> >> With the recent commits, I'm having some t

[Mesa-dev] [PATCH 3/4] docs: Renormalize some extensions.

This fixes some exceptions I have to deal with in mesamatrix.net. The extensions GL_ARB_texture_buffer_object had a comment between "DONE" and the brackets. And the extension GL_KHR_robustness (in GL 4.5 and GLES 3.1) was using "90% done" instead of "in progress". The "90% done" is still here

[Mesa-dev] [PATCH 2/4] docs: Realign the "Status" column.

The "Status" column was misaligned in some GL sections. This is a lot of diffs, but it's only spaces in the end. --- docs/GL3.txt | 278 +-- 1 file changed, 139 insertions(+), 139 deletions(-) diff --git a/docs/GL3.txt b/docs/GL3.txt index

[Mesa-dev] [PATCH 1/4] docs: howto to read and edit GL3.txt

Added a small guide on how to read and edit GL3.txt. I think this would help as much the devs as the users reading this file. --- docs/GL3.txt | 25 - 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/docs/GL3.txt b/docs/GL3.txt index ee7faca..1ed5c1a 100644

[Mesa-dev] [PATCH 0/4] Small changes in GL3.txt (v2)

Hi! With the recent commits, I'm having some trouble parsing the GL3.txt text file for mesamatrix.net. With these set of 4 patches, I'm proposing to rationalize this file a little bit. Rest assure, the content is still exactly the same. Cheers! Romain Failliot (4): docs: howto to read

[Mesa-dev] [PATCH 4/4] docs: Renormalize older extensions.

For older extensions, there is an explanation first and the extension name in brackets, like that: Clamping controls (GL_ARB_color_buffer_float) I inverted that so we have the extension first and then the explanation in brackets, like that: GL_ARB_color_buffer_float (Clamping controls) It

[Mesa-dev] [PATCH] docs: expand "all drivers" to the list of drivers.

At some place, "all drivers" wasn't useful anymore, the "all DONE" list already had all the currently supported drivers. Also, the syntax "all drivers" isn't future proof, if a new drivers comes up (we never know) it will be considered done although by default it might not be. Finally, expanding

[Mesa-dev] [PATCH] docs: expand "all drivers" to the list of drivers.

New patch based on the latest commits. At some place, "all drivers" wasn't useful anymore, the "all DONE" list already had all the currently supported drivers. Also, the syntax "all drivers" isn't future proof, if a new drivers comes up (we never know) it will be considered done although by

[Mesa-dev] [PATCH v2] docs: expand "all drivers" to the list of drivers.

Forget the previous email, apparently I'm still a git padawan... This, is the new patch rebased on master. At some place, "all drivers" wasn't useful anymore, the "all DONE" list already had all the currently supported drivers. Also, the syntax "all drivers" isn't future proof, if a new drivers

[Mesa-dev] Meaning of "DONE (core only)"

Hi! Two extensions have been recently flagged "DONE (core only)". >From what we understood [1], it means that it's done in mesa, but drivers need to implement it. So, first: is that it? And, second: if it is, could we change for the syntax made for it: "DONE ()"? I'll be happy to do the patch

Re: [Mesa-dev] Meaning of "DONE (core only)"

> My take is (and always has been) that the point of GL3.txt is to coordinate > amongst developers, so clarity is paramount. I completely understand and I'm sure we can do both. The problem here is simply that we're mixing dev comments and feature statuses. I'm working on a way to simply edit

Re: [Mesa-dev] [PATCH v2] docs: expand "all drivers" to the list of drivers.

Thanks! I'll send a better formatted email when I'll get home. 2016-04-13 3:11 GMT-04:00 Michel Dänzer <mic...@daenzer.net>: > On 13.04.2016 12:23, Romain Failliot wrote: > > Forget the previous email, apparently I'm still a git padawan... > > This, is the new patch rebas

Re: [Mesa-dev] [PATCH v3] docs: expand "all drivers" to the list of drivers.

Hi Emil! Actually this patch is less about mesamatrix and more about cleaning the file (IMO). By replacing "all drivers" with the actual list of drivers, I've noticed that it was easier to see which drivers are actually completed or not. I also think this will be problematic when new drivers are

[Mesa-dev] [PATCH v3] docs: expand "all drivers" to the list of drivers.

At some place, "all drivers" wasn't useful anymore, the "all DONE" list already had all the currently supported drivers. Also, the syntax "all drivers" isn't future proof, if a new drivers comes up (we never know) it will be considered done although by default it might not be. Finally, expanding

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

Hi! 2017-01-02 15:10 GMT-05:00 Marek Olšák : > Does dmesg or Xorg.0.log show anything? > I don't know if it's really relevant, but here are my `dmesg` and `journalctl -b _COMM=gdm-x-session` ('xorg' files) before and after a session of Dota. I got two glitches and quit Dota

[Mesa-dev] How about vk_features.txt?

Hi! I regularly receive questions about having Mesamatrix tracking the state of Vulkan API for ANV and RADV. I don't think there is a file in mesa repo that state the progression of Vulkan on each driver. So if you're interested, I could generate a base file (xml?) extracting the tag from the

Re: [Mesa-dev] How about vk_features.txt?

king file > for a while. I'm not sure whether or not it's needed but it wouldn't hurt. > > On Sun, Feb 12, 2017 at 6:48 PM, Romain Failliot < > romain.faill...@foolstep.com> wrote: > >> Hi! >> >> I regularly receive questions about having Mesamatrix tracking the

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

2017-01-23 12:43 GMT-05:00 Romain Failliot <romain.faill...@foolstep.com>: > What is your workaround? For me it is to get back to 2516x1440, it seems > to solve the problem, or at least I've never seen a glitch when in this > resolution. > s/2516/2560/ -- Romai

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

2017-01-23 0:06 GMT-05:00 Timothy Arceri : > I can confirm a similar problem. I have the same card and also got a 4K > monitor recently. For me I was running a game in windowed mode (F1 2015 > I think) for a very short amount of time and had some flickering, after > I

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

2017-01-23 22:58 GMT-05:00 Timothy Arceri : > > What is your workaround? > > I don't have one. I don't get a chance to actually play games much so > the card is very unused at this point. The bigger issue I'm having is > Wayland is unusable with my 4K monitor/RX480 and

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

2016-09-13 12:41 GMT-04:00 Marek Olšák : > > BTW, If you update LLVM to a newer version, you also have to re-build > Mesa, because the LLVM version used by Mesa is determined while Mesa > is being built. > > Also, the chance to rage-quit while building LLVM+Mesa is pretty high >

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

-gallium-drivers=radeonsi,r600,swrast --with-dri-drivers= \ > --with-egl-platforms=x11,drm --enable-gles1 --enable-gles2 > > make -j4 > sudo make install > > You'll probably want to delete /usr/lib/$dir/*mesa*/*. That's Ubuntu's > invention that will prevent you from using insta

[Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

Hi! I've just bought myself an RX 480 (because of the open source drivers). I have Fedora 24 with GNOME 3.20, linux 4.7.2, mesa 12.0.2, llvm 3.8.0. I tested Alien: Isolation (that I couldn't even launch with my old HD 6870), but there is a texture bug, see by yourself:

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

Thanks all for your answers! 2016-09-13 5:15 GMT-04:00 Marek Olšák : > Yeah you need LLVM 3.9 not just for this game, but also for many other > games to work correctly. It's due to the fact that some games require > GL 4.3, which is only supported with LLVM 3.9. Some games don't

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

buffers moved) > - num-bytes-moved (TTM overhead as the number of bytes moved) > - num-compilations (compiler invocations) > > There are also a bunch of useful things like various VRAM and GTT > usage stats, GPU-load, etc. > > Marek > > On Tue, Sep 20, 2016 at 1:25 AM, Rom

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

this game with medium video options. In the meantime I'll play more and try to get more screenshots of these kind of situations. Thanks! 2016-09-23 18:21 GMT-04:00 Romain Failliot <romain.faill...@foolstep.com>: > Thanks Marek, I'll test that! > > In the meantime, firstly I fixed an im

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

2016-09-13 13:53 GMT-04:00 Marek Olšák : > LLVM 32-bit: > > mkdir -p build32 > cd build32 > cmake .. -G Ninja -DCMAKE_INSTALL_PREFIX=/usr/llvm/i386-linux-gnu > -DLLVM_TARGETS_TO_BUILD="X86;AMDGPU" -DLLVM_ENABLE_ASSERTIONS=ON > -DCMAKE_BUILD_TYPE=RelWithDebInfo >

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

2016-09-15 16:27 GMT-04:00 Marek Olšák : > Update your gcc I guess? Sorry, I don't know much about LLVM build > requirements. It works with gcc 5.4.0. I'm using a pretty recent gcc, and the 64-bit compilation works like a charm, it's only the 32-bit compilation that has trouble.

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

2016-09-19 18:40 GMT-04:00 Marek Olšák : > Do you mean the PC is frozen for 2 minutes or just occasional hiccups > for 2 minutes? Occasional hiccups for 2 minutes. The game works well, I wander around and, from time to time, it freezes for a random duration between 2 seconds and

[Mesa-dev] Patch for freedreno features

Hi! There's a patch by Rob Clark that sits in bugzilla for while now: https://bugs.freedesktop.org/show_bug.cgi?id=95460 I've just updated it to HEAD. It would be nice to merge it, especially since there hasn't been much changes in features.txt for a while. Cheers! -- Romain "Creak" Failliot

Re: [Mesa-dev] Patch for freedreno features

2017-01-03 10:47 GMT-05:00 Rob Clark : > Hmm, well I guess in future, git-format-patch and attach that to bz.. > but no worries this time, I went ahead and pushed it w/ --author as > Jan suggested Thanks! I'm sorry, I misunderstood, I thought you preferred the patch to be in

Re: [Mesa-dev] Patch for freedreno features

I'll try to do the git patch! I know features.txt isn't the official support source and it is more for the devs to follow on their work, so it's really up to up if you want to add freedreno in features.txt. I simply don't have a device for each driver, that's why I'm parsing features.txt in

Re: [Mesa-dev] Patch for freedreno features

, swr) GL_ARB_gpu_shader5DONE (i965/gen7+) - 'precise' qualifier DONE -- 2.10.1 (Apple Git-78) 2016-12-31 12:26 GMT-05:00 Romain Failliot <romain.faill...@foolstep.com>: > I'll try to do the git patch! > > I kn

[Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

Hi! I've recently bought a 4K display and an RX 480, but I've got some troubles with Dota when using high settings. I've created a thread on Phoronix forum (because maybe other people have the same problem...):

Re: [Mesa-dev] Patch for freedreno features

2017-01-01 16:15 GMT-05:00 Rob Clark : > well, I was trying to not loose authorship/etc from the patch > (although tbh I've lost track of who the original author was).. > http://www.mesa3d.org/devinfo.html#submitting has some suggestions. I went there, I don't think it's a

Re: [Mesa-dev] How about vk_features.txt?

Hi! I'd like to know which information I should extract from this vk.xml file so that we can track the progress of ANV and RADV Vulkan drivers. Thanks! -- Romain "Creak" Failliot ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org

Re: [Mesa-dev] Vulkan extensions

e <airl...@gmail.com> wrote: >> > On 15 September 2017 at 09:12, Jordan Justen <jordan.l.jus...@intel.com> >> wrote: >> >> On 2017-09-14 15:36:10, Romain Failliot wrote: >> >>> Le 14 sept. 2017 6:11 PM, "Bas Nieuwenhuizen" < &g

Re: [Mesa-dev] Vulkan extensions

Le 14 sept. 2017 6:11 PM, "Bas Nieuwenhuizen" a écrit : For vulkan, because 1.0 is the initial version, there are no extensions to implement to get to that version, so having an extensions list would be nonsensical. I don't think it is nonsensical, say the nouveau

Re: [Mesa-dev] Vulkan extensions

2017-09-14 19:19 GMT-04:00 Bas Nieuwenhuizen : > Also you can implement 0% of the feature list and still be vulkan 1.0 > compliant ;) > Oh... is that so? Thanks for all your answers, I apparently didn't understand what "being Vulkan 1.0" meant ;) So if I understand

[Mesa-dev] Vulkan extensions

Hi! I'm working on exposing the vulkan information recently added in features.txt in mesamatrix.net, but there is no extension list under "Vulkan 1.0 - all DONE: anv, radv" There is a couple of command lines in the commit message though:

[Mesa-dev] Mesamatrix donator message

Hi! I received a donation on Mesamatrix with this message with it: > Please fix long-standing bug, not allowing to properly > recognize my Bonaire XT card with glxinfo tool; for now, > it reports Bonaire. See my WineHQ bug: #38921 Bonaire cards don't speak to me much, but if someone is welling