Hmm someting like TESSEVAL is fine by me but I'd prefer something a bit
more descriptive than TESSC/TESSE...
Roland
Am 03.05.2015 um 17:59 schrieb Marek Olšák:
> Renaming everything would be slightly annoying. I personally prefer
> shorter names anyway (TESSC/TESSE, PIPE_SHADER_TESSEVAL, etc.). I
Renaming everything would be slightly annoying. I personally prefer
shorter names anyway (TESSC/TESSE, PIPE_SHADER_TESSEVAL, etc.). I
don't think longer names would make any difference in readability.
Marek
On Sun, May 3, 2015 at 5:06 PM, Ilia Mirkin wrote:
> On Sun, May 3, 2015 at 6:18 AM, Glen
On Sun, May 3, 2015 at 6:18 AM, Glenn Kennard wrote:
> On Sat, 02 May 2015 22:16:24 +0200, Ilia Mirkin
> wrote:
>
>> This series adds tokens and updates some helper gallium functions to
>> know about tessellation. This provides no actual support for
>> tessellation in either core or drivers, howe
On Sat, 02 May 2015 22:16:24 +0200, Ilia Mirkin
wrote:
This series adds tokens and updates some helper gallium functions to
know about tessellation. This provides no actual support for
tessellation in either core or drivers, however this will make it
possible to work on the core and driver pi
This series adds tokens and updates some helper gallium functions to
know about tessellation. This provides no actual support for
tessellation in either core or drivers, however this will make it
possible to work on the core and driver pieces without crazy
interdependencies, as well as be landed se
