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

2016-04-14 Thread Ian Romanick
Sorry for not paying attention sooner... the problem with this is that "all drivers" also means drivers that aren't (and won't be) in the list. It really means *all* drivers. i915 and r300 support ARB_sampler_objects, for example. I think in nearly all cases "all drivers" means that a driver can

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

2016-04-14 Thread Emil Velikov
On 14 April 2016 at 16:48, Romain Failliot wrote: > 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 n

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

2016-04-14 Thread Romain Failliot
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

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

2016-04-14 Thread Emil Velikov
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

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

2016-04-13 Thread Romain Failliot
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