> If we use the sysval, at least 1 is driver spec, 2 can be shared. So could you
> move 2 into the nir dir for sharing with lima?
For sure, I'll try to get a patch for that this weekend :)
-Alyssa
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On Sat, Apr 6, 2019 at 10:18 AM Alyssa Rosenzweig wrote:
>
> Hi,
>
> NIR system values are the preferred method of transferring state like
> this around; the shared transformation pass should be agnostic to the
> underlying uniforms / state tracker / etc. Is there any reason we can't
> share the t
Hi,
NIR system values are the preferred method of transferring state like
this around; the shared transformation pass should be agnostic to the
underlying uniforms / state tracker / etc. Is there any reason we can't
share the transform as I implement it here? (Which makes no assumptions
about unif
So you prefer to use the nir sysval method and implement a per driver version
of viewport transform? As I sended out a patch series for a shared version of
this transform, any feedback on it?
https://patchwork.freedesktop.org/series/58618/
Regards,
Qiang
On Wed, Apr 3, 2019 at 9:50 AM Alyssa Rose
This patch set implements the infrastructure for piping system values
through Panfrost, replacing the prior brittle system of magic uniform
offsets. This infrastructure is used to implement the vertex shader
viewport transformation, which will soon be shared with lima.
Alyssa Rosenzweig (2):
nir
