Hi, I was looking for mechanisms for communicating from the RT side to the non-RT side of my application. As I understand the design philosophy behind RTLinux, the RT side should be as thin as possible, and the amount of code on the RT side should be minimized. To communicate between the two, there are the fifo's, however, they seem to be less then optimal since /dev/rtfxx must be created ahead of time. There is also an implied data transfer between the two which is not necessary if shared memory is used. What I am looking for is simply a way to signal a non-rt posix thread from the rt side. Ideally this would be something like pthread_cond_signal which would be called from the rt side on a conditional variable existing on the non-rt side. I suspect this would be rather challenging to implement, so I was hoping to get some suggestions for alternatives. I could also put more code on the rt side, to minimize rt/non-rt communication, but this doesn't seem like a great way to do things because (a) rebooting because of bad code and (b) module (kernel) code seems to have to be c++ Colin Stewart -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
