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

   tfiga: <u>hverkuil</u>: I think the fact that we take plane lengths from the userspace v4l2_plane in __verify_length() is a bug
   <br> https://elixir.bootlin.com/linux/v5.5-rc2/source/drivers/media/common/videobuf2/videobuf2-v4l2.c#L102
   <br> because the spec clarly says the field is set by the driver
   <br> https://www.kernel.org/doc/html/latest/media/uapi/v4l/buffer.html#struct-v4l2-plane
   ***: hfr has left
   Kwiboo: <u>bbrezillon</u>: I did not test your rkvdec / hantro branch this past weekend, instead I played around with your bus format series and narmstrong yuv420 series and got yuv and 10-bit output to work on my rk3328 to be ready for testing some 10-bit decoding action ;)
   <br> see https://github.com/Kwiboo/linux-rockchip/commits/next-20191213-bus-format for work-in-progress patches, I hope I can test your hantro/rkvdec branch later this week
   bbrezillon: <u>Kwiboo</u>: s/test/debug/ :)
   <br> and thanks for working on 10-bit support
   hverkuil: <u>tfiga</u>: the code is right, the spec is outdated. Userspace should set length for USERPTR and DMABUF since that is not under control of vb2.
   tfiga: <u>hverkuil</u>: DMABUF is definitely under control of vb2, as the buffer is kernel managed and for USERPTR it's arguable that anything else than bytesused is needed for OUTPUT buffers
   <br> I guess for CAPTURE buffers one would to set the limit indeed to avoid overwriting some data
   <br> would want to*
   <br> but I think that's already defined by sizeimage and checked by drivers queue_setup
   mort: so, I just had the venus driver end up stalling a CPU while waiting for a spinlock: https://pastebin.com/va3aS6bZ
   <br> probably in the video decoder part of the driver; the video encoder was running and encoding frames just fine
   ***: benjiG has left
   larkfisherman: Hey guys
   <br> I need to use video4linux2 for writing some applications for frame capturing/processing for my usb camera
   <br> I've been reading through wiki for the last few days but v4l2 seems to be quite huge - can anyone point me in the right direction or give me some resources to start with?
   <br> I'm particularly only interested in usb camera stuff - capabilites, settings, frame capturing, etc...
   ***: larkfisherman has left