 | | Re: signals / legOS internals
|
|
(...) Cool. I will proceed. (...) Yup. I was out of the loop for awhile, and am once again whompin' on this project. (...) That is true. Signals would give the task the opportunity to stop/start tasks under its control, though, without the task that (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) More to the point, it cannot recognize the '(cd' command. Now, why that is, or how you can fix it, I do not know. It would appear to be a problem with make or with your shell. It should just be farming the entire line off to the shell, which (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) No, you should not abandon your implementation - not if you want to use LegOS. I was only explaining how I implemented similar functionality, for the sake of comparison. Regarding Librcx, I might release another version at some point, to add (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
I reinstalled everything and I have progressed to the point of seeing the first-c++.o file and it stops with the following error: -snip- C:\legOS-0.1.7>make h8300-hms-g++ -DCXX -O2 -fno-builtin -fomit-frame-pointer -Wall -Wno-unused -Wno (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) So, should I abandon my implementation? If something every bit as good is already there, it may be silly for me to continue. I haven't looked at Librcx yet, so I don't completely understand how it works. I think one of the original reasons for (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
Ola, I do not see why you persist. I understand that a signal handler is very low level, that it is difficult to use right, that it only allows some things and not others, unless you're very careful. But you still missed my point, which was this: (...) (25 years ago, 25-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) When a frame or character has been received by the IR port it signals an interrupt to the processor. The processor (OS) handles this by invoking an ISR (Interrupt Service Routine). In OSE ISR's are known as interrupt processes and they execute (...) (25 years ago, 25-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) I should add that since many things are vectored in this version of Librcx, overriding functionality is easy for the advanced user to do. For example: extern void (*__event_vector)(void); void my_setup_func() { // ... __event_vector = (...) (25 years ago, 24-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) I think you're missing the point. Now correct me if I'm wrong, Lou -- I believe the intent of the signal mechanism is to allow a way to specify a function to run when a system event occurs: e.g. a message arrives across the IR port. It is (...) (25 years ago, 24-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
I misspoke when I said before that we have semaphores. What I meant was mutexes. We have had mutexes for quite awhile. Certainly long before I started on this signal thing. I started this long enough ago that I don't remember what particular problem (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
