| Brian Silverman | 14fd0fb | 2014-01-14 21:42:01 -0800 | [diff] [blame] | 1 | see ../README.txt for stuff affecting crio and linux code |
| 2 | |
| 3 | The folder is called linux_code because it mainly deals with code that uses the queue system, which only works under GNU/Linux for a variety of reasons, some fundamental (futexes) and some because nobody bothers to fix them. |
| 4 | The layout is designed with multiple linux boxes in mind. |
| 5 | |
| Brian | 74aa260 | 2014-04-02 12:25:14 -0700 | [diff] [blame] | 6 | The code for the linux box that talks the cRIO etc is in ../prime/. |
| Brian Silverman | 14fd0fb | 2014-01-14 21:42:01 -0800 | [diff] [blame] | 7 | |
| 8 | [NOTES] |
| 9 | Any code should call aos::Init() (or aos::InitNRT() for processes that don't need to be realtime) before making any calls to any of the aos functions. |
| 10 | Making calls to any of the aos functions (including aos::Init()) from more than 1 thread per process is not supported, but using fork(2) after some aos functions have been called and then continuing to make aos function calls (without calling one of the exec(3) functions) in both processes is supported. |