Hello yn: I use RTLinux with QT. I have 3 processes in a typical i-386 single CPU control system.
1) A RTLinux process / module 2) A conventional Linux supervisor process wherein I run the bulk of my logic 3) A conventional Linux QT process as a GUI I communicate between my supervisory Linux process and RTLinux via real-time FIFO and in some cases shared memory. I communicate between my supervisory Linux process and the QT GUI via the loopback interface (127.0.0.1), TCP/IP. In an attempt to improve the responsiveness of my supervisory conventional Linux process, I compile the conventional Linux kernel with 1000 HZ time slices and run a ITIMMER_REAL interval timer / signal handler (SIGALRM) with a 1 MS interval. I constantly check the main loop time within this process. When the loop time is short, meaning that we are not doing long calculations etc., I call sleep() within this process hoping that the Linux scheduler will select the QT GUI process to run in the time remaining until the next time slice begins. Similarly, within the RTLinux process and as I am sure everyone else on this list also does, I avoid keeping the processor when not needed. If I have hardware interrupts available, I run the period of the RTLinix process much lower than the conventional process' ITIMMER_REAL to reduce context switching losses and leave more processor time available for the two conventional Linux processes. Wayne Iyuhong ren wrote: > > Dear All, > > Any good ideas on how RTLinux could work together with Qt/Embedded on an > embedded system? Thank a lot. > > Regards, > yh > > -- [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/ -- [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/
