 | | Re: Implementation of Installable Timers
|
|
(...) I'd go with the flag, myself. (...) Its certainly possible for the client timer to reinsert itself - therefore the recurring timer is not strictly required. It could be left out for space reasons. I'd probably either take it out and make it (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Sorry, I'm still just not getting it at all. I have type errors all over the place trying to pass arguments to my task. Could someone please simply email me or post an example of a program that starts, runs two or more threads, and will (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Brickos fun and games!
|
|
Hello. I have finally got gcc 2.95.3 - the official brickos compiler - installed on my computer (SUSE Linux). I can type "make" and compile all the brickos directory fine. firmdl3 works fine. BUT, dll doesn't seem to work. When I use dll to download (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) It would seem reasonable to check the location of the struct; if in kernel memory, don't remove; if in user memory, remove. However, you could add a flag to the timer struct which could use T_KERNEL and T_USER flags. (...) I looked quickly (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) You are right. I found in an app that I was using that if I pressed the run / stop button, my task would be killed, and leave a dangling timer - which would usually blow the little brick into the weeds :o) I 'solved' it in a crude way by (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
