vidi

Module pipelines

Source
Expand description

General V4L2 handling.

This module should take over a lot of things from the uvc module because UVC should only be specialized to do things that aren’t applying to every camera.

It’s still unclear what the interface to a specialized module should be. Some drivers use special formats for exchanging statistics and creating data to feed back to the hardware with them. Those formats are well-known and described at runtime, so perhaps they can be just a different pipeline config rather than an entirely new driver.

Structs§

  • A representation of a camera that is ready to stream or streaming.
  • An ID of a camera, unique between cameras on the same system, same across instances of this camera. Undefined across library versions or consecutive runs.
  • Information about present camera The camera is defined as a sensor which can reach an output, without specifying any path between them. The camera may fail to get acquired if all outputs are already acquired by other cameras.
  • A way to stream buffers
  • A detected camera device.

Enums§

Constants§

  • Put the entry function to every supported kind of camera here.

Traits§

  • An exclusive handle to a mutable camera resource.
  • This trait is only responsible for releasing the lock when dropped
  • A camera which has been detected, but not yet exclusively acquired for changing.

Type Aliases§