05-31-2020, 05:36 AM
I believe that if the modules were not loaded, those device files were not created. But I did verify that. I'm using Debian Bullseye (mobian).
The modules I built with dkms are the only ones with that name under /lib/modules , so there's no mixup with a module of another source.
Note that I used the existing debian/ directory in that git repository to build a deb package and installed it.
debian@pinephone:~$ /sbin/lsmod | grep _linux
binder_linux 81920 0
ashmem_linux 20480 0
debian@pinephone:~$ ls -l /dev/binder /dev/ashmem
crw------- 1 root root 10, 62 May 31 09:09 /dev/ashmem
crw------- 1 root root 511, 0 May 31 09:09 /dev/binder
Using the following rules file seems to do the trick:
DEVPATH=="*/ashmem", MODE="0666"
DEVPATH=="*/binder*", MODE="0666"
The modules I built with dkms are the only ones with that name under /lib/modules , so there's no mixup with a module of another source.
Note that I used the existing debian/ directory in that git repository to build a deb package and installed it.
debian@pinephone:~$ /sbin/lsmod | grep _linux
binder_linux 81920 0
ashmem_linux 20480 0
debian@pinephone:~$ ls -l /dev/binder /dev/ashmem
crw------- 1 root root 10, 62 May 31 09:09 /dev/ashmem
crw------- 1 root root 511, 0 May 31 09:09 /dev/binder
Using the following rules file seems to do the trick:
DEVPATH=="*/ashmem", MODE="0666"
DEVPATH=="*/binder*", MODE="0666"