Laurent Pinchart <laurent.pinchart@xxxxxxxxxxx> writes: > That's right, but if four applications open the device at the same time, thet > will all request 32 buffers and not 8 as they don't know about each other. The driver can grant 8 buffers only through ... > > For mmap capture, it may not be hard to add this in a backward compatible > > manner. But no software supports this. From a point of view of a hardware > > manufacture or user, it's a huge drawback if your hardware time domain > > multiplexing doesn't work with nvrec, motion, mencoder, and so on. > > Why would you want to encode from a single time multiplexed stream ? I doubt > MPEG encoding would achieve outstanding results if 4 video inputs are > multiplexed into the stream. And all existing software will work with the > hardware, as they won't set the extra bit in the v4l2_buffer.flags, and so > the driver will not time multiplex inputs. Fully agree. Doing the multiplexing with multiple file handles and "virtual" inputs creates some non-trivial scheduling issues. With *one* application capturing from multiple inputs this is trivial as the application has explicitly switch inputs by setting the (new) v4l2_buffer.input field. Gerd -- You have a new virus in /var/mail/kraxel
