Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] hwcontext_vulkan: fix exporting multi-plane DRM modifiers
Date: Sat, 3 May 2025 09:24:05 +0200
Message-ID: <45b9d7ee-3a64-4d38-980b-bd8ae06b9025@lynne.ee> (raw)
In-Reply-To: <CAAOCm6q6PHtTBpkE5x1T8_1aXYP57oDMHdMPQ+5HU3yqkEH_CA@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 965 bytes --]

On 03/05/2025 04:39, Russell Greene wrote:
> Is this documented anywhere? Should I maybe have a fixed sized stack
> buffer and fallback to an allocation if it's just a rule of thumb that
> it'll be less than some known small number. I just somehow doubt this
> is in the vulkan spec or any sort of guaranteed....



vkGetPhysicalDeviceToolPropertiesEXT(dev, nb, array)
If pToolProperties is NULL, then the number of tools currently active on 
physicalDevice is returned in pToolCount. Otherwise, pToolCount must 
point to a variable set by the application to the number of elements in 
the pToolProperties array, and on return the variable is overwritten 
with the number of structures actually written to pToolProperties. If 
pToolCount is less than the number of currently active tools, at most 
pToolCount structures will be written.

It's in the spec. Different function, but all functions which write to 
an array follow the same signature.

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-05-03  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01  5:05 Russell Greene
2025-05-02  0:09 ` Lynne
2025-05-03  2:39   ` Russell Greene
2025-05-03  7:24     ` Lynne [this message]
2025-05-03 15:01       ` Russell Greene
2025-05-03 15:24         ` Lynne
2025-05-03 16:11           ` Russell Greene
2025-05-03 16:29             ` Russell Greene
2025-05-10 14:56               ` Russell Greene
  -- strict thread matches above, loose matches on Subject: below --
2025-04-29 20:33 Russell Greene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45b9d7ee-3a64-4d38-980b-bd8ae06b9025@lynne.ee \
    --to=dev@lynne.ee \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git