From: Samuel Pitoiset <samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: "unknown fragment shader param 17" error on NV46 when running glxgears
Date: Mon, 11 Apr 2016 12:36:38 +0200 [thread overview]
Message-ID: <570B7E36.2050704@gmail.com> (raw)
In-Reply-To: <570B7823.5060104-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 04/11/2016 12:10 PM, Hans de Goede wrote:
> Hi,
Hi,
>
> While trying to reproduce:
> https://bugzilla.redhat.com/show_bug.cgi?id=1325667
>
> I also gave glxgears a quick test with mesa master, this
> resulted in the following errors being printed to the
> terminal from which glxgears was started :
>
> unknown fragment shader param 17
> unknown fragment shader param 17
> unknown fragment shader param 17
> unknown fragment shader param 17
> unknown fragment shader param 17
>
> I would like to fix these, any hints where I need to look ?
>
It seems like that PIPE_SHADER_CAP_INTEGERS for frag shaders is missing
in nv30_screen_get_shader_param(). This won't fix your issue but this
will silence this debug message though.
> Regards,
>
> Hans
>
>
> _______________________________________________
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/nouveau
--
-Samuel
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2016-04-11 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 10:10 "unknown fragment shader param 17" error on NV46 when running glxgears Hans de Goede
[not found] ` <570B7823.5060104-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-11 10:36 ` Samuel Pitoiset [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570B7E36.2050704@gmail.com \
--to=samuel.pitoiset-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.