Searched refs:imported (Results 1 – 25 of 46) sorted by relevance
12
7 When submitting work that operates on memory imported from a Direct3D 1112 They can: only be used if the imported resource was created with the26 objects which were imported from Direct3D 11 resources.37 objects which were imported from Direct3D 11 resources.
85 * Imports a raw buffer handle to create an imported buffer handle for use92 * buffer. It must be imported to create an imported handle first.95 * imported handle. It must also support importing the same raw handle96 * multiple times to create multiple imported handles. The imported handle101 * may actually have been imported in the process. importBuffer must treat109 * NO_RESOURCES when the raw handle cannot be imported at111 * @return buffer is the imported buffer handle and has the type123 * the imported handle. For example, if the imported handle was created
87 * Imports a raw buffer handle to create an imported buffer handle for use94 * buffer. It must be imported to create an imported handle first.97 * imported handle. It must also support importing the same raw handle98 * multiple times to create multiple imported handles. The imported handle103 * may actually have been imported in the process. importBuffer() must treat112 * - `NO_RESOURCES` if the raw handle cannot be imported due to124 * the imported handle. For example, if the imported handle was created155 * Calculates the transport size of a buffer. An imported buffer handle is a158 * data at the tail when serializing the imported buffer handle.161 * when sending an imported buffer handle. The mapper must support both
23 The implementation may: not acquire a reference to the imported Screen27 imported is being used.52 * pname:buffer is the QNX Screen buffer which will be imported.77 memory type which the specified Screen buffer can: be imported as.104 when used with an image bound to memory imported from pname:buffer.
14 These QNX Screen buffer objects may: be imported into slink:VkDeviceMemory16 An slink:VkImage or slink:VkBuffer can: be bound to the imported37 A slink:VkDeviceMemory imported from a QNX Screen buffer has no way to86 properties, so Vulkan images bound to memory imported from a QNX Screen92 When creating an image that will be bound to an imported QNX Screen buffer,
60 * STORAGE_KEY is used to denote that a key generated or imported is a key used for storage61 * encryption. Keys of this type can either be generated or imported or secure imported using
45 on imported semaphores that are in an invalid state?51 However, this could cause security concerns when using imported semaphores,
24 associated with an imported Vulkan memory object when submitting command
48 Using the memory object imported from a host allocation that is already68 6) Can the same host allocation be imported multiple times into a given
38 specific support usage within Vulkan for imported native memory objects, or
42 imported.
23 associated with an imported Vulkan memory object when submitting command
46 imported.
39 specific support usage within Vulkan for imported native memory objects, or
153 properties need to be exported and imported when sharing images across161 dedicated allocation mechanism to associate the exported and imported memory
79 * Get the transport size of a buffer. An imported buffer handle is a raw82 * runtime data at the tail when serializing the imported buffer handle.85 * data when sending an imported buffer handle. The mapper must support
101 * Imports a raw buffer handle to create an imported buffer handle for use108 * buffer. It must be imported to create an imported handle first.111 * imported handle. It must also support importing the same raw handle112 * multiple times to create multiple imported handles. The imported handle117 * may actually have been imported in the process. importBuffer() must treat126 * - `NO_RESOURCES` if the raw handle cannot be imported due to138 * the imported handle. For example, if the imported handle was created169 * Calculates the transport size of a buffer. An imported buffer handle is a172 * data at the tail when serializing the imported buffer handle.175 * when sending an imported buffer handle. The mapper must support both
8 On Fuchsia, when allocating memory that may: be imported from another13 External memory on Fuchsia is imported and exported using VMO handles of100 type which the specified handle can be imported as.
46 // android.hardware.tests.foo@1.0::IFooCallback, since bar@1.0::IFooCallback is not imported.
1272 instances other than that corresponding to the memory object imported.1273 Implementations must: also ensure accessing imported memory which has not1280 How exported and imported memory is isolated is left to the implementation,1437 specified when the payload being imported was created1444 payload being imported was allocated1464 those specified when the payload being imported was created1694 pname:handle is the VMO handle to the imported external memory1758 and the memory is not an imported1760 …NDROID_external_memory_android_hardware_buffer+VK_QNX_external_memory_screen_buffer[or an imported]1772 and the memory is not an imported[all …]
2182 pname:fence must: not currently have its payload replaced by an imported2185 that imported payload's handle type was included in2280 pname:fence must: not currently have its payload replaced by an imported2283 that imported payload's handle type was included in2410 It indicates that the client can only wait on the imported fence or2610 <<synchronization-fences-importing, payload imported>> with temporary2777 a new fence was created with the same handle but the imported payload.2806 If the fence was using a temporarily imported payload, the fence's prior2880 When a fence is using an imported payload, its2895 Because the exportable handle types of an imported fence correspond to its[all …]
94 BufferHandle(GraphicsTestsBase& testBase, native_handle_t* handle, bool imported, in BufferHandle() argument98 mImported(imported), in BufferHandle()
36 wait semaphores imported by the presentation engine using the equivalent of
100 the external handle type of the imported memory must: also have been set
94 the external handle type of the imported memory must: also have been set