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 added. I've heard about OpenSWR recently that is apparently an alternative to llvmpipe, I guess this driver could be added in this file, doesn't it? Here, the "all drivers" lines will activate GL extensions for this new driver whether it's true or not. I completely understand that this file is mainly meant for the devs. But from what I've seen, even the devs themselves aren't sure about the meaning of some lines in this file (I remember previous emails where I asked the difference between "DONE" and "DONE ()" and not everyone agreed on the signification ;)). So, to me, structuring this file is not just for mesamatrix but also for the global understanding of everyone. I hope I'll be of more help in the future. Right now it's GL3.txt and mesamatrix, later it might be drivers optimizations ;) Cheers! 2016-04-14 10:18 GMT-04:00 Emil Velikov <emil.l.veli...@gmail.com>: > Hi Romain, > > While I appreciate the effort put in mesamatrix, I feel that things > are steering towards the wrong direction here. > > That is, the file is (was?) meant to coordinate between developers on > who's doing what, thus adding/changing policies in order to make it > easier to be read/parsed by a PHP/other script feels ... strange. > Afaics the current format does produce reasonable results, right ? > > At the end of the day feel free to do as you wish, although I would > kindly invite you to chip in with the html files in docs. Imho they > are ones that could use your time/skills ;-) > > Regards > Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
