On Wed, 6 Jul 2016, Ian Sutton wrote: > * tipru comes disabled by default. Attempts to enable tipru, and > following modification of the instruction/data/shared memory > spaces, are only allowed when the system's securelevel(7) is equal > or lesser than zero. When the system's securelevel(7) is greater > than zero the PRU cores may only be started or halted via the > PRUCTL ioctl(2) call, and the driver itself may be disabled via the > PRUKILL ioctl(2) call which effectively halts and prevents the PRU > from performing any actions until the system is rebooted.
That sounds like a reasonable compromise - it would let the admin load code to the PRUs in rc.securelevel for later use, or set kern.securelevel=0 in sysctl.conf if they wanted to do development on a multi-user system.
