On Mon, Aug 20, 2018 at 7:20 PM Marek Olšák wrote:
>
> On Mon, Aug 20, 2018 at 7:06 PM Rob Clark wrote:
> >
> > On Mon, Aug 20, 2018 at 6:54 PM Bas Nieuwenhuizen
> > wrote:
> > >
> > > On Tue, Aug 21, 2018 at 12:38 AM, Marek Olšák wrote:
> > > > On Fri, Aug 10, 2018 at 9:26 AM Rob Clark wrote:
On Mon, Aug 20, 2018 at 7:06 PM Rob Clark wrote:
>
> On Mon, Aug 20, 2018 at 6:54 PM Bas Nieuwenhuizen
> wrote:
> >
> > On Tue, Aug 21, 2018 at 12:38 AM, Marek Olšák wrote:
> > > On Fri, Aug 10, 2018 at 9:26 AM Rob Clark wrote:
> > >>
> > >> Used internally in freedreno/ir3 for the vec2 value t
On Mon, Aug 20, 2018 at 6:54 PM Bas Nieuwenhuizen
wrote:
>
> On Tue, Aug 21, 2018 at 12:38 AM, Marek Olšák wrote:
> > On Fri, Aug 10, 2018 at 9:26 AM Rob Clark wrote:
> >>
> >> Used internally in freedreno/ir3 for the vec2 value that hw passes to
> >> shader to use as coordinate for bary.f (vary
On Tue, Aug 21, 2018 at 12:38 AM, Marek Olšák wrote:
> On Fri, Aug 10, 2018 at 9:26 AM Rob Clark wrote:
>>
>> Used internally in freedreno/ir3 for the vec2 value that hw passes to
>> shader to use as coordinate for bary.f (varying fetch) instruction.
>> This is not the same as SYSTEM_VALUE_FRAG_C
On Fri, Aug 10, 2018 at 9:26 AM Rob Clark wrote:
>
> Used internally in freedreno/ir3 for the vec2 value that hw passes to
> shader to use as coordinate for bary.f (varying fetch) instruction.
> This is not the same as SYSTEM_VALUE_FRAG_COORD.
>
> Signed-off-by: Rob Clark
> ---
> Up until now, we
Used internally in freedreno/ir3 for the vec2 value that hw passes to
shader to use as coordinate for bary.f (varying fetch) instruction.
This is not the same as SYSTEM_VALUE_FRAG_COORD.
Signed-off-by: Rob Clark
---
Up until now, we'd been hard-coding the location of this value (ie. to
r0.xy), mo
