As Seb says, the properties in the hal module are thin wrappers around rtapi_is_xxx.
hal.is_userspace is simply always the inverse of hal.is_kernelspace, which is just rtapi_is_kernelspace(). This is true for RTAI and false for uspace. hal.is_sim is simply the inverse of hal.is_rt, which is just rtapi_is_realtime(). The semantics of rtapi_is_realtime() are a bit troublesome as detailed in the manpage--and I'd love for someone to improve this. For RTAI, the implementation of rtapi_is_realtime should check the running kernel (via uname(2)) against RTAPI_KERNEL_VERSION; for uspace, it should stat(2) rtapi_app and test whether st_mode has the S_ISUID bit set. (for RTAI, checking the mode of the module helper is not worth doing; this missing +s just indicates misconfiguration) Jeff ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
