All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: Andreas Boll <andreas.boll.dev@gmail.com>
Cc: mesa-dev@lists.freedesktop.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH][8.0] nvfx: handle some unknown PIPE_CAPs
Date: Tue, 30 Oct 2012 18:33:23 +0100	[thread overview]
Message-ID: <1351618403.1434.49.camel@tellur> (raw)
In-Reply-To: <1351616616-29106-1-git-send-email-andreas.boll.dev@gmail.com>

Am Dienstag, den 30.10.2012, 18:03 +0100 schrieb Andreas Boll:
> fixes these warnings:
> 
> nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
> nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
> nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
> nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
> nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=47442
> Bugzilla: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674965
> Signed-off-by: Andreas Boll <andreas.boll.dev@gmail.com>

While this doesn't really fix anything:
Reviewed-by: Lucas Stach <dev@lynxeye.de>
> ---
> 
> Note: This patch is only for the 8.0 branch.
> Compile tested only.
> 
>  src/gallium/drivers/nvfx/nvfx_screen.c |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/src/gallium/drivers/nvfx/nvfx_screen.c b/src/gallium/drivers/nvfx/nvfx_screen.c
> index b4a1b3a..26c2d8d 100644
> --- a/src/gallium/drivers/nvfx/nvfx_screen.c
> +++ b/src/gallium/drivers/nvfx/nvfx_screen.c
> @@ -88,6 +88,12 @@ nvfx_screen_get_param(struct pipe_screen *pscreen, enum pipe_cap param)
>  	case PIPE_CAP_MAX_TEXEL_OFFSET:
>  	case PIPE_CAP_CONDITIONAL_RENDER:
>  	case PIPE_CAP_TEXTURE_BARRIER:
> +	case PIPE_CAP_MAX_STREAM_OUTPUT_BUFFERS:
> +	case PIPE_CAP_MAX_STREAM_OUTPUT_SEPARATE_COMPONENTS:
> +	case PIPE_CAP_MAX_STREAM_OUTPUT_INTERLEAVED_COMPONENTS:
> +	case PIPE_CAP_STREAM_OUTPUT_PAUSE_RESUME:
> +	case PIPE_CAP_TGSI_CAN_COMPACT_VARYINGS:
> +	case PIPE_CAP_TGSI_CAN_COMPACT_CONSTANTS:
>                  return 0;
>  	case PIPE_CAP_MIXED_COLORBUFFER_FORMATS:
>                  return 0;

  reply	other threads:[~2012-10-30 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 17:03 [PATCH][8.0] nvfx: handle some unknown PIPE_CAPs Andreas Boll
2012-10-30 17:33 ` Lucas Stach [this message]
2012-10-30 17:49   ` Andreas Boll

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=1351618403.1434.49.camel@tellur \
    --to=dev@lynxeye.de \
    --cc=andreas.boll.dev@gmail.com \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.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.