This is needed if you can only handle point sprites on certain varyings but not others. This is the case for nv30- and nvc0-based GPUs, which is why the cap was introduced.
If your GPU does not have such restrictions, you can safely remove the cap. -ilia On Fri, Mar 15, 2019 at 12:25 AM Alyssa Rosenzweig <aly...@rosenzweig.io> wrote: > > I don't know why this was on to begin with...? > > Signed-off-by: Alyssa Rosenzweig <aly...@rosenzweig.io> > --- > src/gallium/drivers/panfrost/pan_screen.c | 3 --- > 1 file changed, 3 deletions(-) > > diff --git a/src/gallium/drivers/panfrost/pan_screen.c > b/src/gallium/drivers/panfrost/pan_screen.c > index 9cd65ca8ff8..9672048bca8 100644 > --- a/src/gallium/drivers/panfrost/pan_screen.c > +++ b/src/gallium/drivers/panfrost/pan_screen.c > @@ -195,9 +195,6 @@ panfrost_get_param(struct pipe_screen *screen, enum > pipe_cap param) > case PIPE_CAP_TEXTURE_BUFFER_OFFSET_ALIGNMENT: > return 0; > > - case PIPE_CAP_TGSI_TEXCOORD: > - return 1; /* XXX: What should this me exactly? */ > - > case PIPE_CAP_PREFER_BLIT_BASED_TEXTURE_TRANSFER: > return 0; > > -- > 2.20.1 > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
