Skip to content

feat(vdo): Expose map and frame additions from SDK 12.11.0 - #262

Open
vsem-azamat wants to merge 1 commit into
AxisCommunications:mainfrom
vsem-azamat:feat/vdo-sdk-12.11
Open

vsem-azamat wants to merge 1 commit into
AxisCommunications:mainfrom
vsem-azamat:feat/vdo-sdk-12.11

Conversation

@vsem-azamat

Copy link
Copy Markdown
Contributor

Part of #244.

Adds Map: Clone, Map::{get,set}_quad32{i,u} with plain Quad32i/Quad32u structs instead of the bindgen unions, StreamBuffer::utc_timestamp and StreamBuffer::is_contiguous.

The AVIF variants and VdoWdrMode already come through the vdo-sys re-exports, so they need no changes here.

Not covered: VdoChunk, VdoZipStreamGdr, the vdo_channel_* removals and the typed stream constructors (vdo_stream_{rgb,nv12,y800}_new), which this crate does not use yet. I would like to hear how you would prefer the typed constructors to fit into StreamBuilder before adding them.

Device tests are extended but not yet run on hardware.

Part of AxisCommunications#244.

- `Map` implements `Clone` via `vdo_map_clone`.
- `Map::{get,set}_quad32{i,u}` with plain `Quad32i`/`Quad32u` structs
  instead of the bindgen unions.
- `StreamBuffer::utc_timestamp` (`vdo_frame_get_utc_timestamp`).
- `StreamBuffer::is_contiguous` (`vdo_buffer_is_contiguous`), documented
  as the precondition for `as_slice` and `data_copy`.

The new `VdoFormat`/`VdoFrameType` AVIF variants and `VdoWdrMode` need no
changes: the enums are re-exported from `vdo-sys` as is. The remaining
items in the checklist (`VdoChunk`, `VdoZipStreamGdr`, `vdo_channel_*`,
typed stream constructors) are not used by this crate yet.
@vsem-azamat
vsem-azamat requested a review from a team as a code owner September 3, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant