HORIZON HASKELLDocslts/ghc-9.14.x45dd5372026-10-11Search names, modules, packages, or :: a typeCtrl K

GHC 9.14.1 · lts/ghc-9.14.x · 45dd537 · 2026-10-11

Modulevulkan-3.27GHC2021

Vulkan.Extensions.VK_QNX_external_memory_screen_buffer

Name

VK_QNX_external_memory_screen_buffer - device extension

VK_QNX_external_memory_screen_buffer

Name String

VK_QNX_external_memory_screen_buffer

Extension Type

Device extension

Registered Extension Number

530

Revision

1

Ratification Status

Not ratified

Extension and Version Dependencies

VK_KHR_sampler_ycbcr_conversion          and

VK_KHR_external_memory          and

VK_KHR_dedicated_allocation      or

Vulkan Version 1.1 and VK_EXT_queue_family_foreign

Contact

Other Extension Metadata

Last Modified Date

2023-05-17

IP Status

No known IP claims.

Contributors

  • Mike Gorchak, QNX / Blackberry Limited

  • Aaron Ruby, QNX / Blackberry Limited

Description

This extension enables an application to import QNX Screen Screen_buffer objects created outside of the Vulkan device into Vulkan memory objects, where they can be bound to images and buffers.

Some Screen_buffer images have implementation-defined /external formats that may/ not correspond to Vulkan formats. Sampler Y′CBCR conversion can be used to sample from these images and convert them to a known color space.

Screen_buffer is strongly typed, so naming the handle type is redundant. The internal layout and therefore size of a Screen_buffer image may depend on native usage flags that do not have corresponding Vulkan counterparts.

New Commands

New Structures

New Enum Constants

Version History

  • Revision 1, 2023-05-17 (Mike Gorchak)

    • Initial version

See Also

No cross-references are available

Document Notes

For more information, see the Vulkan Specification.

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

  • 8 types
  • 1 value
  • Packagevulkan-3.27
  • Exports11
  • LanguageGHC2021
  • LicenceBSD-3-Clause
  • SourceVK_QNX_external_memory_screen_buffer.hs
valuegetScreenBufferPropertiesQNX
  1. :: (Extendss ScreenBufferPropertiesQNX a, PokeChain a, PeekChain a, MonadIO io)
  2. => Device

    device is the logical device that will be importing buffer.

    device must be a valid Device handle

  3. -> Ptr Screen_buffer

    buffer is the QNX Screen buffer which will be imported.

    buffer must be a valid QNX Screen buffer

    buffer must be a valid pointer to a valid Screen_buffer value

  4. -> io (ScreenBufferPropertiesQNX a)
#

vkGetScreenBufferPropertiesQNX - Get Properties of External Memory QNX Screen Buffers

Return Codes

Success
Failure

See Also

VK_QNX_external_memory_screen_buffer, Device, ScreenBufferPropertiesQNX

datadata ImportScreenBufferInfoQNX
#

VkImportScreenBufferInfoQNX - Import memory from a QNX Screen buffer

Description

The implementation may not acquire a reference to the imported Screen buffer. Therefore, the application must ensure that the object referred to by buffer stays valid as long as the device memory to which it is imported is being used.

Valid Usage

Valid Usage (Implicit)

Structure Chaining

Extends the structure

See Also

VK_QNX_external_memory_screen_buffer, StructureType

Constructors

Instances6Eq, Show, Storable, FromCStruct, ToCStruct, Zero
datadata ScreenBufferPropertiesQNX (es :: [Type])
#

VkScreenBufferPropertiesQNX - Properties of External Memory QNX Screen Buffers

Valid Usage (Implicit)

  • pNext must be NULL or a pointer to a valid instance of ScreenBufferFormatPropertiesQNX

  • The sType value of each structure in the pNext chain must be unique

See Also

VK_QNX_external_memory_screen_buffer, DeviceSize, StructureType, getScreenBufferPropertiesQNX

Constructors

Instances5Extensible, Show, FromCStruct, ToCStruct, Zero
datadata ScreenBufferFormatPropertiesQNX
#

VkScreenBufferFormatPropertiesQNX - Structure describing the image format properties of a QNX Screen buffer

Description

If the QNX Screen buffer has one of the formats listed in the QNX Screen Format Equivalence table, then format must have the equivalent Vulkan format listed in the table. Otherwise, format may be FORMAT_UNDEFINED, indicating the QNX Screen buffer can only be used with an external format. The formatFeatures member must include FORMAT_FEATURE_SAMPLED_IMAGE_BIT and should include FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT and FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT.

Structure Chaining

Extends the structure

See Also

VK_QNX_external_memory_screen_buffer, ChromaLocation, ComponentMapping, Format, FormatFeatureFlags, SamplerYcbcrModelConversion, SamplerYcbcrRange, StructureType

Constructors

Instances5Show, Storable, FromCStruct, ToCStruct, Zero
datadata ExternalFormatQNX
#

VkExternalFormatQNX - Structure containing a QNX Screen buffer external format

Description

If externalFormat is zero, the effect is as if the ExternalFormatQNX structure was not present. Otherwise, the image will have the specified external format.

Structure Chaining

Extends the structures

See Also

VK_QNX_external_memory_screen_buffer, StructureType

Constructors

Instances6Eq, Show, Storable, FromCStruct, ToCStruct, Zero
datadata PhysicalDeviceExternalMemoryScreenBufferFeaturesQNX
#

VkPhysicalDeviceExternalMemoryScreenBufferFeaturesQNX - Structure describing QNX Screen Buffer features that can be supported by an implementation

Members

The members of the PhysicalDeviceExternalMemoryScreenBufferFeaturesQNX structure describe the following features:

Description

'

Features

Functionality

screenBufferImport

ImportScreenBufferInfoQNX

Always supported1

getScreenBufferPropertiesQNX

,

ScreenBufferPropertiesQNX

,

ScreenBufferFormatPropertiesQNX

,

ExternalFormatQNX

Functionality Supported for QNX Screen Buffer Features

1

Functionality in this row is always available.

The Functionality supported for QNX Screen buffer features table summarizes the functionality enabled by the PhysicalDeviceExternalMemoryScreenBufferFeaturesQNX structure. Each entry in the body of the table summarizes the functionality that can be used when the given features are supported and enabled. This summarizes Valid Usage statements that are added elsewhere in this specification.

If the PhysicalDeviceExternalMemoryScreenBufferFeaturesQNX structure is included in the pNext chain of the PhysicalDeviceFeatures2 structure passed to getPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. If the application wishes to use a Device with any features described by PhysicalDeviceExternalMemoryScreenBufferFeaturesQNX, it must add an instance of the structure, with the desired feature members set to TRUE, to the pNext chain of DeviceCreateInfo when creating the Device.

Structure Chaining

Extends the structures

See Also

VK_QNX_external_memory_screen_buffer, Bool32, StructureType

Constructors

Instances6Eq, Show, Storable, FromCStruct, ToCStruct, Zero