Home
last modified time | relevance | path

Searched refs:images (Results 1 – 25 of 206) sorted by relevance

123456789

/hardware/google/gfxstream/guest/mesa/src/vulkan/runtime/
Dvk_pipeline.c215 _mesa_sha1_update(&ctx, &rstate->images, sizeof(rstate->images)); in vk_pipeline_hash_shader_stage()
267 rs->images = VK_PIPELINE_ROBUSTNESS_IMAGE_BEHAVIOR_DEVICE_DEFAULT_EXT; in vk_pipeline_robustness_state_fill()
276 rs->images = shader_info->images; in vk_pipeline_robustness_state_fill()
285 rs->images = pipeline_info->images; in vk_pipeline_robustness_state_fill()
301 if (rs->images == VK_PIPELINE_ROBUSTNESS_IMAGE_BEHAVIOR_DEVICE_DEFAULT_EXT) in vk_pipeline_robustness_state_fill()
302 rs->images = vk_device_default_robust_image_behavior(device); in vk_pipeline_robustness_state_fill()
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/antora/
DMakefile47 ./images/*.svg \
58 ./images/tile_image.svg \
63 antora/modules/ROOT/images \
70 antora/modules/proposals/images \
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_NV_corner_sampled_image.adoc19 extension refers to as "`corner-sampled`" images.
37 * The minimum level size is 2x2 for 2D images and 2x2x2 for 3D images.
57 aspect of the image organization and referred to such images as
58 "`corner-sampled images`".
71 . Do integer texel coordinates have a different range for corner-sampled images?
77 . Do unnormalized sampler coordinates work with corner-sampled images? Are there any functional dif…
DVK_KHR_display_swapchain.adoc27 1) Should swapchains sharing images each hold a reference to the images, or
28 should it be up to the application to destroy the swapchains and images in
32 The lifetime of presentable images is already complex enough.
39 respecify the mode or create a new swapchain and presentable images.
50 4) How can applications create multiple swapchains that use the same images?
67 images could be built up one at a time.
105 ** Allow creating multiple swapchains that share the same images using a
DVK_QNX_external_memory_screen_buffer.adoc21 memory objects, where they can be bound to images and buffers.
23 Some code:_screen_buffer images have implementation-defined _external
25 Sampler {YCbCr} conversion can: be used to sample from these images and
DVK_KHR_swapchain_mutable_format.adoc22 This extension allows processing of swapchain images as different formats to
27 presentable images with a different format than the one used to create the
43 This extension requires `VK_KHR_maintenance2` and presentable images of
DVK_KHR_swapchain.adoc44 of the presentable images?
47 Unlike standard images, the implementation will allocate the memory backing
50 2) What operations are allowed on presentable images?
55 3) Does this extension support MSAA presentable images?
58 Presentable images are always single-sampled.
59 Multi-sampled rendering must use regular images.
64 4) Does this extension support stereo/multi-view presentable images?
69 All presentable images in a given swapchain use the same array size.
71 5) Are the layers of stereo presentable images half-sized?
92 7) Does flink:vkAcquireNextImageKHR block if no images are available?
[all …]
DVK_KHR_maintenance2.adoc33 * Allow creating images with usage flags that may not be supported for the
36 * Allow creating uncompressed image views of compressed images.
39 * Adds two new image layouts for depth stencil images to allow either the
51 aspect(s) of multi-aspect images can: be accessed as input attachments.
DVK_EXT_shader_image_atomic_int64.adoc28 these operations on images as well.
37 64-bit integer atomic support is guaranteed for optimally tiled images with
DVK_KHR_separate_depth_stencil_layouts.adoc21 This extension allows image memory barriers for depth/stencil images to have
25 To support depth/stencil images with different layouts for the depth and
DVK_NV_linear_color_attachment.adoc20 This extension expands support for using ename:VK_IMAGE_TILING_LINEAR images
32 the formats their images views are created with have
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_display_swapchain/
Dcreate_shared_swapchains.adoc7 …SharedSwapchainsKHR',desc='Create multiple swapchains that share presentable images',type='protos']
15 swapchains that share presentable images are created by calling:
35 presentable images must: match between all the swapchains.
38 images, swapchain creation will fail with the result code
44 the presentable images can: continue to be used.
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/style/
Dmisc.adoc8 Images used in the Vulkan documents must be kept in the directory `images/`
14 This allows other people to easily edit your images in the future.
16 image editors have been observed to produce images incompatible with the PDF
21 In most cases, images are included as standalone figures and should occupy
29 As the PDF dimensions are more restrictive, images should not exceed these
40 images are scaled down lies is about 30-something pixels lower than that;
53 Text in images should usually appear at 12 point type so as to match that in
64 The font and color scheme used for existing images (black, red, and 50%
65 gray) should be used for changes and new images whenever reasonable to do
99 Please ensure that you build the PDF before submitting any new images,
/hardware/google/gfxstream/guest/mesa/src/vulkan/wsi/
Dwsi_common_headless.c268 struct wsi_headless_image images[0]; member
279 return &chain->images[image_index].base; in wsi_headless_swapchain_get_wsi_image()
300 if (!chain->images[i].busy) { in wsi_headless_swapchain_acquire_next_image()
303 chain->images[i].busy = true; in wsi_headless_swapchain_acquire_next_image()
327 chain->images[image_index].busy = false; in wsi_headless_swapchain_queue_present()
340 if (chain->images[i].base.image != VK_NULL_HANDLE) in wsi_headless_swapchain_destroy()
341 wsi_destroy_image(&chain->base, &chain->images[i].base); in wsi_headless_swapchain_destroy()
459 size_t size = sizeof(*chain) + num_images * sizeof(chain->images[0]); in wsi_headless_surface_create_swapchain()
495 &chain->images[i].base); in wsi_headless_surface_create_swapchain()
499 chain->images[i].busy = false; in wsi_headless_surface_create_swapchain()
Dwsi_common_win32.cpp108 struct wsi_win32_image images[0]; member
432 ((uintptr_t)win32_image - (uintptr_t)chain->images) / in wsi_create_dxgi_image_mem()
587 wsi_win32_image_finish(chain, allocator, &chain->images[i]); in wsi_win32_swapchain_destroy()
609 return &chain->images[image_index].base; in wsi_win32_get_wsi_image()
625 assert(chain->images[index].state == WSI_IMAGE_DRAWING); in wsi_win32_release_images()
626 chain->images[index].state = WSI_IMAGE_IDLE; in wsi_win32_release_images()
646 if (chain->images[i].state == WSI_IMAGE_IDLE) { in wsi_win32_acquire_next_image()
648 chain->images[i].state = WSI_IMAGE_DRAWING; in wsi_win32_acquire_next_image()
655 if (chain->images[index].state == WSI_IMAGE_DRAWING) { in wsi_win32_acquire_next_image()
657 assert(chain->images[index].state == WSI_IMAGE_QUEUED); in wsi_win32_acquire_next_image()
[all …]
Dwsi_common_x11.c1110 struct x11_image images[0]; member
1221 return &chain->images[image_index].base; in x11_get_wsi_image()
1252 if (chain->images[i].pixmap == idle->pixmap) { in x11_handle_dri3_present_event()
1253 chain->images[i].busy = false; in x11_handle_dri3_present_event()
1270 struct x11_image *image = &chain->images[i]; in x11_handle_dri3_present_event()
1272 x11_present_complete(chain, &chain->images[i]); in x11_handle_dri3_present_event()
1421 if (!chain->images[i].busy) { in x11_acquire_next_image_poll_find_index()
1423 xshmfence_await(chain->images[i].shm_fence); in x11_acquire_next_image_poll_find_index()
1425 chain->images[i].busy = true; in x11_acquire_next_image_poll_find_index()
1579 xshmfence_await(chain->images[image_index].shm_fence); in x11_acquire_next_image_from_queue()
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_swapchain_maintenance1.adoc23 * Impossible to release acquired images without presenting them
39 mode does not affect the actual swapchain images and their associated memory.
52 This requires swapchain implementations to allocate memory for all images
54 This is costly both in startup time, and potentially memory if all images are
68 application has acquired images from the old swapchain that it is no longer
70 However, it is unable to release those images before recreating the swapchain.
116 Each present mode may require a different number of images.
126 ** The swapchain would then allocate as many images to satisfy all present
128 * Increase the number of swapchain images as necessary when present mode is
156 present mode that uses that many images is used.
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_swapchain/
Dwsi.adoc15 A swapchain is an abstraction for an array of presentable images that are
17 The presentable images are represented by sname:VkImage objects created by
20 surfaces) is displayed at a time, but multiple images can: be queued for
43 The presentable images of a swapchain are owned by the presentation engine.
66 The presentation engine controls the order in which presentable images are
73 return of images after presentation.
75 referencing all of the images in the swapchain at initialization time,
108 pname:pCreateInfo->minImageCount presentable images.
110 While acquired by the application, presentable images can: be used in any
111 way that equivalent non-presentable images can: be used.
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_GOOGLE_display_timing/
Dqueries.adoc8 ename:VK_PRESENT_MODE_FIFO_KHR so that presentable images are updated during
13 However, synchronizing the presentation of images with the RC does not
26 They need to know when presentable images were actually presented, and when
75 The rate at which an application renders and presents new images is known as
88 pname:refreshDuration), an application needs to determine when its images
96 This will create visual anomalies, because the images will not be displayed
100 presentation engine to not present images any sooner than every 33.33ms.
110 Adjustments to a larger IPD because of late images should happen quickly,
114 and if pname:presentMargin is consistently large, over multiple images.
217 images presented with fname:vkQueuePresentKHR.
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/scripts/
DcompImages.sh24 cp images/*.svg $img1
36 cp images/*.svg $img2
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/
Dcopy_bufferimage_to_imagebuffer_not_both_image_common.adoc6 // Common to commands copying from images to buffers, or buffers to images
Dcopy_bufferimage_to_imagebuffer_buffer_alignment_common.adoc6 // Common to commands copying from images to buffers, or buffers to images
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_swapchain_maintenance1/
DSwapchainPresentModeInfo.adoc25 slink:VkSwapchainPresentModeInfoEXT, images that have already been queued
28 The current image being queued for presentation and subsequent images will
48 subsequent images.
54 and subsequent images are appended to the FIFO queue and presented
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_QNX_external_memory_screen_buffer/
Dqnx_screen_buffer.adoc58 QNX Screen buffers may: represent images using implementation-specific
64 representation, images with external formats must: only be used as sampled
65 images, must: only be sampled with a sampler that has {YCbCr} conversion
75 enable consistent handling of images from sources that might use either
86 properties, so Vulkan images bound to memory imported from a QNX Screen
89 be ename:VK_TRUE for images created with
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_present_wait/
Dpresent_wait.adoc10 outstanding images queued for presentation, need to have a method of being
22 applications can discover when images were presented, but only

123456789