From e0095548c02200d00a4edbd5bb1a28a32c324c5b Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Fri, 24 Feb 2012 17:46:44 +0100 Subject: [PATCH] svga: fix use of SVGA3D_x vs. PIPE_FORMAT_x in svga_is_format_supported() MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Two of the switch cases used PIPE_FORMAT_ tokens instead of SVGA3D_ tokens. As it happens, the token values are equal for these formats so there's no net change. Reviewed-by: José Fonseca Reviewed-by: Jakob Bornecrantz --- src/gallium/drivers/svga/svga_screen.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/svga/svga_screen.c b/src/gallium/drivers/svga/svga_screen.c index 8d47e69006c..a4de4932652 100644 --- a/src/gallium/drivers/svga/svga_screen.c +++ b/src/gallium/drivers/svga/svga_screen.c @@ -358,8 +358,8 @@ svga_is_format_supported( struct pipe_screen *screen, /* Often unsupported/problematic. This means we end up with the same * visuals for all virtual hardware implementations. */ - case PIPE_FORMAT_B4G4R4A4_UNORM: - case PIPE_FORMAT_B5G5R5A1_UNORM: + case SVGA3D_A4R4G4B4: + case SVGA3D_A1R5G5B5: return FALSE; default: -- 2.30.2