Subject:
|
LNP Packet Handlers on RCX
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Thu, 19 Oct 2000 05:08:50 GMT
|
Viewed:
|
1158 times
|
| |
|
|
I remember reading somewhere a while back, when I first started dabbling
with LNP, that LNP handlers on the RCX side were called from interrupts
and therefore doing things like memory allocation, msleep, heavy
processing, etc. were not good ideas. Now I'm working on this LNP guide
and I want to confirm this before I start spouting it to the masses, and I
can't find anything about it. The LNP docs are sparse, and neither the
header files nor the LNP source files say anything about it. Did I just
make that up, or is this a real limitation that simply isn't
well-documented?
--
"Say not, 'I have found the truth,' but rather, 'I have found a truth.'
"Say not, 'I have found the path of the soul.' Say rather, 'I have met the
soul walking upon my path.'" -- Khalil Gibran
Mike Ash - <http://www.mikeash.com/>, <mailto:mail@mikeash.com>
|
|
Message has 2 Replies:
 | | Re: LNP Packet Handlers on RCX
|
| Michael- I seem to recall something about LNP not being completely thread safe. However, there is no documentation on that at all. Stig Neilsson (if he is around) may be a good person to ask, since he has studied the threading model in detail, and (...) (24 years ago, 19-Oct-00, to lugnet.robotics.rcx.legos)
| | | Re: LNP Packet Handlers on RCX
|
| (...) In legOS v0.2.3 and probably in v0.2.4 they are still called from the interrupt handler (rx_handler). (...) The interrupt handling should be fast, hence any heavy proccessing in lnp_handler is discouraged. Msleep, malloc and similiar functions (...) (24 years ago, 19-Oct-00, to lugnet.robotics.rcx.legos)
|
6 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
