[Home]History of Uspace

LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org

Revision 12 . . August 17, 2014 4:50 pm by JeffEpler
Revision 11 . . July 30, 2014 12:41 pm by JeffEpler
Revision 10 . . July 30, 2014 12:40 pm by JeffEpler
Revision 9 . . July 26, 2014 9:23 am by JeffEpler
Revision 8 . . July 22, 2014 7:32 am by JeffEpler
Revision 7 . . July 22, 2014 7:26 am by JeffEpler
Revision 6 . . July 21, 2014 12:05 pm by JeffEpler
Revision 5 . . July 21, 2014 8:05 am by JeffEpler
Revision 4 . . July 6, 2014 11:32 am by JeffEpler
Revision 3 . . July 6, 2014 11:25 am by JeffEpler
Revision 2 . . July 6, 2014 11:24 am by JeffEpler
Revision 1 . . July 3, 2014 6:21 am by JeffEpler
  

Difference (from prior major revision) (no other diffs)

Added: 70a71,84

What kind of system is this?



While the <html><rtapi_xxx.h></html> headers provide the portability APIs required by most realtime components, sometimes it's necessary to make decisions based on the details of the system. Here are some checks that you may find it useful to perform.

Preprocessor checks



* Building "realtime" code? defined(RTAPI)
** APIs specified as "realtime only" (e.g., rtapi_parport_get) are available
* Building "userspace" code? defined(ULAPI)
** Not all RTAPI APIs available
* Building on a Linux operating system? defined(__linux__)
* Building this code in kernel space? defined(__KERNEL__)

Runtime checks



* Realtime resides in kernelspace? rtapi_is_kernelspace()
* Underlying OS provides realtime guarantees? rtapi_is_realtime()


LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org
Search:
Published under a Creative Commons License