[02:18] *** darvon has quit IRC (Remote host closed the connection)
[13:59] *** Whoopie has quit IRC (Ping timeout: 258 seconds)
[14:07] *** cybrNaut has quit IRC (Changing host)
[14:23] *** ayaka has quit IRC (Read error: Connection reset by peer)
[19:53] <koike> Hi, I am reading about the Video Overlay API and I am finding it a bit confusing (at least for me) https://linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/dev-overlay.html
[19:53] <koike> So for example, if I have a camera, I can open the file descriptor (fd_cap1) and configure the format with S_FMT and request buffers of type V4L2_BUF_TYPE_VIDEO_CAPTURE as I normally would
[19:53] <koike> Then If the device supports the Overlay interface, I could open another file descriptor (fd_over1), configure the overlay with S_FMT/S_FBUF and I could request buffers of type V4L2_BUF_TYPE_VIDEO_OVERLAY and this will permit me to inject a "window" in the captured image of the camera, right?
[19:53] <koike> Then for exmaple, I could write an image of an elephant at fd_over1 and when capturing the image from fd_cap1 I would see my camera image in the background with my elephant in front, is that correct?
[19:53] <koike> If I open another file descriptor to inject another overlay image (fd_over2), how the driver knows the clipping aread between both frame buffers? which one comes in front of the other? If I use chromakey for exmaple, how can userspace pass to the driver a rectangle of a certain color ?
[19:53] <koike> (Or maybe this question doesn't make sense and I understood everything wrong?)
[19:54] <koike> s/aread/area