#v4l 2020-04-10,Fri

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***taliho has left "The Lounge - https://thelounge.chat" [03:03]
................................................................................................... (idle for 8h13mn)
ezequielghverkuil: ping. [11:16]
............... (idle for 1h14mn)
dafna2anyone knows why is the priv field exit only in v4l2_pix_format and not in v4l2_pix_format_mplane ? [12:30]
...... (idle for 25mn)
jmondidafna2: give it refers to V4L2_CAP_EXT_PIX_FORMAT and V4L2_PIX_FMT_PRIV_MAGIC which does not seems used at the moment seems like legacy stuff
likely before mplane was introduced ?
[12:55]
koikeandrzej_p: (sorry, arriving late for the loopback discussion) there is a patch in vimc adding output device, and with the configfs patch, to get a loopback you just need to create an output device, a capture, add a link between them and that is it. I believe tonyk even tested loopback, but the missing point was that we required changes in v4l2-compliance
dafna2: jmondi: if I understand correctly, the priv field is a way to extend the api if required (to use those raw_bytes[] that we add in the end)
[12:55]
jmondikoike: Hi Helen, the documentation refers to " remaining fields of the struct v4l2_pix_format, also called the extended fields" which I don't see mentioned anywhere else..
could they be ycbcr_enc, hsv_enc etc, which where intially only 'optionally' supported ? From what I see V4L2_PIX_FMT_PRIV_MAGIC and V4L2_CAP_EXT_PIX_FORMAT are now unconditionally set, so I don't think the private field should be considered anymore. But dunno, was not there at the time :)
[13:08]
................................ (idle for 2h37mn)
***benjiG has left [15:46]
.......................................................... (idle for 4h47mn)
kenperkins_ has left [20:33]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)