[libcamera-devel] use of v4l2-compat.so

Nicolas Dufresne nicolas at ndufresne.ca
Mon Jun 22 23:55:50 CEST 2020


Le lundi 22 juin 2020 à 15:31 +0300, George Kiagiadakis a écrit :
<cut>

> For libcamera, they way I see it, it would make sense to go with a
> design similar to the ALSA one. libcamera could have backends for its
> frontend API, either through plugins or hardcoded in the library. In one
> backend it would directly access the device, while in the other one it
> would go through PipeWire. This would avoid duplicating the API.
> 
> Please don't hesitate to ask me if you have further questions related to
> PipeWire.

As you may know, with libcamera, camera are no longer single stream, and frames
are requested. But to get the stream configured, the application need to do some
hanshake with the "CameraManager" (trying to simplify). So the question is what
does PipeWire offer (if any) to help carry this handsake to the server side
CameraManager ?

The pull base scheduling is very interesting, since we could probably map well
with request, though is there mechanism to attach some data with the request in
pull mode ?

Nicolas



More information about the libcamera-devel mailing list