Home
last modified time | relevance | path

Searched refs:commandbuffer (Results 1 – 9 of 9) sorted by relevance

/third_party/skia/site/docs/dev/chrome/
Dcommandbuffer.md23 Both tools have a `commandbuffer` config which can be used with the `--config`
/third_party/ffmpeg/libavformat/
Drtmpproto.c2244 uint8_t commandbuffer[64]; in handle_notify() local
2250 if (ff_amf_read_string(&gbc, commandbuffer, sizeof(commandbuffer), in handle_notify()
2254 if (!strcmp(commandbuffer, "onMetaData")) { in handle_notify()
2287 if (!strcmp(commandbuffer, "@setDataFrame")) { in handle_notify()
3030 uint8_t commandbuffer[64]; in rtmp_write() local
3035 if (!ff_amf_read_string(&gbc, commandbuffer, sizeof(commandbuffer), in rtmp_write()
3037 if (!strcmp(commandbuffer, "onMetaData") || in rtmp_write()
3038 !strcmp(commandbuffer, "|RtmpSampleAccess")) { in rtmp_write()
/third_party/vk-gl-cts/external/vulkan-docs/src/chapters/VK_NV_cuda_kernel_launch/
Dmodule.adoc72 (i.e. dispatch) from a commandbuffer.
/third_party/skia/src/gpu/mtl/
DGrMtlGpu.mm269 // Besides the current commandbuffer, we also add the finishedCallback to the newest outstanding
270 // commandbuffer. Our contract for calling the proc is that all previous submitted cmdbuffers
273 // finished. It is safe to only add the proc to the newest outstanding commandbuffer cause that
/third_party/vk-gl-cts/external/vulkan-docs/src/chapters/
Dcmdbuffers.txt105 [[commandbuffer-lifecycle-diagram]]
414 [[commandbuffer-allocation]]
Dcmdbuffers.adoc105 [[commandbuffer-lifecycle-diagram]]
621 [[commandbuffer-allocation]]
/third_party/mesa3d/docs/relnotes/
D19.3.0.rst518 - radv: Split out commandbuffer submission.
/third_party/vk-gl-cts/external/vulkan-docs/src/
DChangeLog.txt4759 <<commandbuffer-lifecycle-diagram, Lifecycle of a command buffer>>
9606 * Editorial fixes for <<commandbuffer-allocation,Command Buffer
DChangeLog.adoc8274 <<commandbuffer-lifecycle-diagram, Lifecycle of a command buffer>>
13120 * Editorial fixes for <<commandbuffer-allocation,Command Buffer