Bug 111393 - Warnings about Formats with "inconsistent channel types"
Summary: Warnings about Formats with "inconsistent channel types"
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-13 15:35 UTC by Mauro Rossi
Modified: 2019-08-21 06:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Mauro Rossi 2019-08-13 15:35:19 UTC 
Hi,
I'm building mesa with radv and I'm getting these warnings
printed out from gfx10_format_table.h generator (gfx10_format_table.py)

Gen Header: libmesa_radv_common_32 <= gfx10_format_table.h
Format VK_FORMAT_D16_UNORM_S8_UINT has inconsistent channel types: set([1]) set([False, True]) set([False, True])
Format VK_FORMAT_D24_UNORM_S8_UINT has inconsistent channel types: set([1]) set([False, True]) set([False, True])
Format VK_FORMAT_D32_SFLOAT_S8_UINT has inconsistent channel types: set([1, 4]) set([False]) set([False, True])

Could you please check what is the problem?
Mauro
Comment 1 zefkerrigan 2019-08-15 16:57:31 UTC 
I have exactly the same problem.(In reply to Mauro Rossi from comment #0)
> Hi,
> I'm building mesa with radv and I'm getting these warnings
> printed out from gfx10_format_table.h generator (gfx10_format_table.py)
> 
> Gen Header: libmesa_radv_common_32 <= gfx10_format_table.h
> Format VK_FORMAT_D16_UNORM_S8_UINT has inconsistent channel types: set([1])
> set([False, True]) set([False, True])
> Format VK_FORMAT_D24_UNORM_S8_UINT has inconsistent channel types: set([1])
> set([False, True]) set([False, True])
> Format VK_FORMAT_D32_SFLOAT_S8_UINT has inconsistent channel types: set([1,
> 4]) set([False]) set([False, True])
> 
> Could you please check what is the problem?
> Mauro

I have exactly the same problem.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.