| 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 | |
| 6 | The one that talks to the cRIO etc is called the prime. We have multiple explanations for that name: |
| 7 | It is the primary controller. |
| 8 | PRIME/Primary Robot Intelligent Management Entity |
| 9 | Represents Optimus Prime, one of the good transformers who battle the bad ones that 254 names robots after. |
| 10 | It is easy to type and doesn't conflict with anything else common for tab-completion. |
| 11 | It's not hardware-specific. |
| 12 | |
| 13 | [NOTES] |
| 14 | 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. |
| 15 | 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. |