<!-- 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>

   ***: lyakh has quit IRC (Ping timeout: 480 seconds)
   <br> eelstrebor has quit IRC (Quit: Ex-Chat)
   <br> camus1 has joined #linux-media
   <br> camus has quit IRC (Ping timeout: 480 seconds)
   <br> nh has joined #linux-media
   <br> nh has quit IRC ()
   <br> camus has joined #linux-media
   <br> camus1 has quit IRC (Ping timeout: 480 seconds)
   <br> camus has quit IRC (Ping timeout: 480 seconds)
   <br> jm_h has joined #linux-media
   <br> camus has joined #linux-media
   <br> camus has quit IRC (Remote host closed the connection)
   <br> camus has joined #linux-media
   <br> djrscally has joined #linux-media
   <br> ao2 has joined #linux-media
   <br> jarthur has joined #linux-media
   <br> xiaer1922 has joined #linux-media
   <br> xiaer1921 has quit IRC (Ping timeout: 480 seconds)
   <br> xiaer1922 is now known as xiaer1921
   <br> camus1 has joined #linux-media
   <br> camus has quit IRC (Read error: Connection reset by peer)
   <br> svarbanov has joined #linux-media
   <br> jarthur has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
   <br> camus has joined #linux-media
   <br> camus1 has quit IRC (Ping timeout: 480 seconds)
   <br> lucaceresoli has joined #linux-media
   <br> camus has quit IRC (Remote host closed the connection)
   <br> camus has joined #linux-media
   <br> Eugen_H has quit IRC (Remote host closed the connection)
   <br> padovan has joined #linux-media
   <br> BrianG61UK has quit IRC (Read error: Connection reset by peer)
   <br> camus1 has joined #linux-media
   <br> camus has quit IRC (Read error: Connection reset by peer)
   dv_: https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/dev-mem2mem.html contains documentation for en- and decoders, but what about mem2mem devices that do colorspace conversion, scaling, 90-degree rotations?
   <br> is there documentation for those?
   ndufresne: No specific documentation, general documentation applies of course
   <br> This is something in my todo, but didn't have time yet, and kernel writer strictly don't care apparently
   <br> (interop must be terrible atm)
   <br> but I think Hans do have few tests even though not strictly specified in v4l2-compliance
   ***: eelstrebor has joined #linux-media
   <br> svarbanov has quit IRC (Ping timeout: 480 seconds)
   <br> camus has joined #linux-media
   <br> camus1 has quit IRC (Read error: Connection reset by peer)
   <br> svarbanov has joined #linux-media
   <br> gouchi has joined #linux-media
   <br> camus has quit IRC ()
   <br> camus has joined #linux-media
   <br> Moarc has quit IRC (Quit: i znowu NADMUCHAŁ BALONA)
   <br> Moarc has joined #linux-media
   <br> camus has quit IRC ()
   <br> camus has joined #linux-media
   <br> svarbanov has quit IRC (Ping timeout: 480 seconds)
   <br> lucaceresoli has quit IRC (Ping timeout: 480 seconds)
   <br> camus has quit IRC ()
   <br> jarthur has joined #linux-media
   <br> lucaceresoli has joined #linux-media
   <br> jm_h has quit IRC (Remote host closed the connection)
   <br> svarbanov has joined #linux-media
   <br> lucaceresoli has quit IRC (Ping timeout: 480 seconds)
   <br> lucaceresoli has joined #linux-media
   <br> lucaceresoli has quit IRC (Quit: Leaving)
   <br> djrscally has quit IRC (Quit: Konversation terminated!)
   <br> djrscally has joined #linux-media
   <br> svarbanov has quit IRC (Ping timeout: 480 seconds)
   <br> gouchi has quit IRC (Remote host closed the connection)
   <br> ao2 has quit IRC (Quit: Leaving)
   djrscally: A question about VIDIOS_ENUM_FRAMEINTERVALS; it looks like most drivers just give the default frame interval for the currently selected mode, but with blanking that's not necessarily the only supported frame rate
   <br> Should it be setting Continuous in that case?
   pinchartl: for sensor drivers ?
   djrscally: oui
   pinchartl: I wouldn't implement VIDIOS_ENUM_FRAMEINTERVALS at all
   <br> as the frame rate is controlled through blanking and clocks
   <br> not directly
   djrscally: let me make sure I'm giving the ioctl the right name here...
   <br> Because that makes me think that no I'm not
   <br> Bah, I'm not of course, I should have been looking at VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL
   <br> Sorry!
   pinchartl: same answer, you shouldn't implement that :-)
   djrscally: Aaaaand if I'm amending a driver that already has it; I can delete it instead of wracking my brain over the best way to fix it?
   pinchartl: that's what I would recommend, but someone may object
   <br> I'd give it a try at least :-)
   <br> which driver is that ?
   djrscally: I like this answer
   <br> ov8865
   <br> It's the goofy HTS where it's lower than output_size_x. I think possibly Paul's idea was to make the numbers work for a 2 lane configuration, but it seemed better to me in that case to go with the higher HTS that tallies with what everyone seems to expect and just calculate the FPS it can support based on the lanes that are found in the bus config
   <br> A side effect of which is the need to fix / delete that callback
   pinchartl: deleting it sounds like the easiest option, right ? :-)
   djrscally: oh yeah I'm 100% onboard
   <br> deleting code is my favourite thing
   pinchartl: I'm afraid we need to at some too, from time to time
   djrscally: Begrudgingly
   ***: djrscally has quit IRC (Ping timeout: 480 seconds)