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

   ***: syoung has quit IRC (Quit: leaving)
   <br> anon2313 has left
   fdk17: Hello, I had a question about using videobuf2-dma-contig and memmap buffers and how to verify that the mapped buffers are continguous in physical memory (and on Intel a warning message saying that writeback is set).  I hope this is a good place.
   pinchartl: <u>fdk17</u>: feel free to ask :-)
   fdk17: Okay.  Thanks.  So in the V4L2 driver that I'm writing I need to capture to contiguous physical memory.  This in is kernel v4.19.y.  But it doesn't appear that DMA_ATTR_FORCE_CONTIGUOUS is being used.  Does using videobuf2-dma-contig mean that continguous physical memory is being used or that in the userland the memory will look contiguous?
   ezequielg: <u>hverkuil</u>: you mentioned running smatch on the rkvdec review and i'm really curious how you are using smatch.
   <br> if anyone else has tips on smatch or other static analyzers, i'd love to hear that.
   ***: indy has quit IRC (Ping timeout: 244 seconds)
   <br> uajain has quit IRC (*.net *.split)
   <br> mjasny has quit IRC (*.net *.split)
   <br> sailus has quit IRC (*.net *.split)
   <br> Muzer has quit IRC (*.net *.split)
   <br> mripard has quit IRC (*.net *.split)