 | | Re: signals / legOS internals
|
|
(...) In OSE interrupt processes (first class processes, that is why we don't call them ISR's) use OS mechanisms (usually messages) to communicate with normal processes. The OS handles all update of shared data structures (such as message queues). A (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: signals / legOS internals
|
|
(...) This is the same thing as most modern RTOS use, called various things. The terminology I use for this is FLIH/SLIH (first level interrupt handler and second level interrupt handler). Coupled with lock priority inheritance, it makes for a very (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
 | | RE: New Challenge
|
|
(...) Good idea Todd, but there is a hitch. What surface is the dumbell on? Can the bot pick up the dumbell? Can the dumbell be in a cart? etc.... Cheers, Ralph Hempel - P.Eng ---...--- Outside of a dog, a book is a man's best friend. Indside of a (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
|
| |
 | | Re: signals / legOS internals
|
|
(...) This second methed doesn't really solve anything since you still have to communicate with the compute thread from the receive thread. (...) But what can you actually do in the signal handler? Modify the state of the state of the executing (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: signals / legOS internals
|
|
(...) Because they are useful at times, and Markus directed me to implement them. I think the upcoming network code is going to use them, too (at least, that's what I heard). Just 'cause they're there doesn't mean you have to use them. (...) How do (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|