<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   ***: mrpops2ko has quit IRC ()
   <br> mrpops2ko has joined #linux-media
   <br> zhentao10 has joined #linux-media
   <br> zhentao10 has quit IRC ()
   <br> ao2 has joined #linux-media
   <br> frieder has joined #linux-media
   <br> mvaittin has joined #linux-media
   <br> GBenji has joined #linux-media
   <br> sgruszka has joined #linux-media
   <br> lexano has joined #linux-media
   <br> charrus_ has quit IRC (Ping timeout: 480 seconds)
   <br> charrus has joined #linux-media
   <br> mvaittin has quit IRC (Ping timeout: 480 seconds)
   <br> sylpe has joined #linux-media
   sylpe: Hi there! sailus jmondi
   <br> What is the interest to ref /schemas/media/video-interface-devices.yaml in my schema? Well In fact, I see the interest to "inherit" of "rotation" and "orientation" properties.... The real question would be why don't all image sensors reference video-interface-devices.yaml?
   sailus: <u>sylpe</u>: That's probably for historical reasons.
   <br> The file is newer than many (or most?) bindings and not all bindings have been updated yet.
   sylpe: Ok, if there's no other reason, I should ref video-interface-devices.yaml in my schema .
   sailus: Yes, please.
   <br> (Assuming the device is a sensor, that is.)
   ***: frieder has quit IRC (Ping timeout: 480 seconds)
   sylpe: It is :-)
   ***: jmassot_ has joined #linux-media
   <br> frieder has joined #linux-media
   <br> jmassot has quit IRC (Ping timeout: 480 seconds)
   <br> Ampera has quit IRC (Ping timeout: 480 seconds)
   <br> ten1572377432463050 has quit IRC (Remote host closed the connection)
   <br> ten1572377432463050 has joined #linux-media
   <br> jmassot_ has quit IRC (Quit: Leaving)
   <br> jmassot has joined #linux-media
   <br> charrus_ has joined #linux-media
   <br> charrus has quit IRC (Ping timeout: 480 seconds)
   <br> charrus has joined #linux-media
   <br> charrus_ has quit IRC (Ping timeout: 480 seconds)
   <br> jmassot_ has joined #linux-media
   <br> jmassot has quit IRC (Ping timeout: 480 seconds)
   <br> frieder has quit IRC (Remote host closed the connection)
   <br> Ampera has joined #linux-media
   <br> jernej has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
   <br> jernej has joined #linux-media
   <br> ten1572377432463050 has quit IRC (Remote host closed the connection)
   <br> ten1572377432463050 has joined #linux-media
   <br> jmassot has joined #linux-media
   <br> jmassot_ has quit IRC (Ping timeout: 480 seconds)
   <br> GBenji has quit IRC (Ping timeout: 480 seconds)
   <br> GBenji has joined #linux-media
   <br> GBenji has left
   pinchartl: <u>hverkuil</u>: how far is the current implementation of the request API from being able to support multiple clients for devices that have multiple video nodes ?
   <br> is it something already done by codecs ? or do we support multiple clients only with a single video node, using the M2M API ?
   ***: eelstrebor has joined #linux-media
   <br> ao2 has quit IRC (Quit: Leaving)
   <br> sgruszka has quit IRC (Ping timeout: 480 seconds)
   <br> ao2 has joined #linux-media
   <br> ao2 has quit IRC (Quit: Leaving)
   <br> danitool has joined #linux-media
   <br> sgruszka has joined #linux-media
   <br> sgruszka has quit IRC ()
   <br> Moarc has quit IRC (Quit: i znowu NADMUCHAŁ BALONA)
   <br> Moarc has joined #linux-media
   <br> tmerciai has quit IRC (Remote host closed the connection)
   <br> jernej has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
   <br> jernej has joined #linux-media
   ndufresne: <u>pinchartl</u>: it's a loaded question
   <br> M2M only have a single video node, multiple video node is not supported
   <br> To do multi-client m2m, the clients need to share their fds, in practice, I don't see why anyone would do that
   <br> M2M is very different, since each time you open the video device you get a different context, I've never tried to see what happens if you use the same request for two context, it will probably do something, perhaps spit warnings ...
   pinchartl: <u>ndufresne</u>: I'm considering the request API to implement multi-context support for ISPs
   <br> I'm trying to evaluate how much extra work would be needed
   ***: charrus_ has joined #linux-media
   <br> charrus has quit IRC (Ping timeout: 480 seconds)
   <br> lexano has quit IRC (Ping timeout: 480 seconds)