Closed danergo closed 11 months ago
Could be an issue about no enough permission. Check devices under /dev/dma_heap
with command:
# ls -lh /dev/dma_heap/
They are expect to be readable for normal users.
Thanks for the tip, here is my output:
$ ls -lh /dev/dma_heap
total 0
crw------- 1 root root 251, 4 Aug 7 2022 cma
crw------- 1 root root 251, 5 Aug 7 2022 cma-uncached
crw------- 1 root root 251, 0 Aug 7 2022 system
crw------- 1 root root 251, 1 Aug 7 2022 system-dma32
crw------- 1 root root 251, 2 Aug 7 2022 system-uncached
crw------- 1 root root 251, 3 Aug 7 2022 system-uncached-dma32
I tried changing their owner to root:video
, and gave permission of 0666
, but it didn't work. I had to change it to 0777
which is quite open is this the correct way of giving permission to this feature? :)
The permission is control by Linux system level, by rule.d
, not by MPP. You can Google how to change this setting. I'm not familiar with it.
I think permission of 666
is enough, and there is no need to change owener and group to video
.
I want to use ffmpeg to use HW acc for decode and encode on NanoPi R5C.
Basic configuration and build of ffmpeg:
ffmpeg test:
Journal:
Kernel: 5.10.110
OS: Debian Bullseye
Can you please help me?