#v4l 2020-02-20,Thu

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

WhoWhatWhen
tfigahverkuil: I'll try to take a look a bit later [08:20]
hverkuilezequielg: the rkvdec driver only needs a follow-up patch adding a MAINTAINERS entry, and then I can post a PR for it. Can you do that today? (PS: don't forget to also refer to the binding file in the MAINTAINERS entry, it's easy to forget about that one) [08:27]
............ (idle for 55mn)
ezequielg: see my follow-up mails, a v6 is needed after all. [09:22]
ezequielghverkuil: ok. I will try today. [09:28]
.................. (idle for 1h25mn)
hverkuil: I'll post today after my daily meetings :) [10:53]
........................................................................................ (idle for 7h16mn)
dafna2hverkuil: hi, the rkisp1 driver fails in the compliance tests, in the case of using userptr when streaming
the error is because the vb2_dma_contig_memops expect the buffers allocated by the userspace to be alligned
I wonder if it should be fixed in v4l-utils, or either just drop the support for userptr?
[18:09]
hverkuilDrop support for userptr. userptr support makes no sense for drivers based on vb2_dma_contig. Support for userptr for dma_contig exists primarily for old drivers that abused userptr giving it pointers to known contiguous data (usually from a special memory pool).
I'm not even sure if those drivers are still in use, I thought it was mostly soc-camera that did this.
Tomorrow I'll check to see who still uses this and if support for this can be killed.
[18:12]
dafna2ok, and if it can you will send a patch removing support from all drivers with contig_dma?
in that case I don't have to write a patch just for rkisp1
[18:20]
hverkuilThat's putting the cart before the horse :-)
It's a simple patch for rkisp1: just remove VB2_USERPTR for any dma_config queue.
[18:26]
dafna2:-) ok [18:37]

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