The rmgr driver module
rmgr
Description:
The rmgr provides a ressource database feature (similar to the Xressource)
to the kernel. Each ressource can have its own access permissions if accessed
from the user interface.
If a ressource is accessed a callback can be invoked so actions can be invoked
depending on a ressource's value. Callbacks cannot be specified
from the user interface.
Kernel ressources are stored in a global ressource database that can be
accessed from user space using the rmanip program.
The rmgr can be configured using the Kernel ressource database.
Driver inodes:
The driver inode in /dev is usually created by
mknod /dev/rmgr c major minor
If another major is needed it can be specified by the
rmgr_major option to insmod:
insmod rmgr.o rmgr_major=new_major
Driver inodes:
All driver generated with LDDK have debugging information
compiled into the code that can be configured with the dbgMask
option to insmod. The bits of dbgMask specifies the debugging verbosity:
- Bit-0 Flag for setting all options=on
- Bit-1 function entrys
- Bit-2 function exits
- Bit-3 branches
- Bit-4 data given to functions
- Bit-5 interrupts
- Bit-6 register info
- Bit-7 reserved
For example:
insmod rmgr.o dbgMask=0x06
logs all function entrys and exits to the kernel log daemon.
Sun Dec 13 14:32:19 1998