Dear Friends,
I am working in a company which creates pSOS applications in the telecom
sector.
A project trainee under me, Sumit, is trying to create a pSOS Simulation
kit for RTLinux so as to be able to demonstate the capabilities of RTLinux
as a proper RTOS of choice for future projects. For this, he is trying to
write wrappers for the most used system calls in the code that our company
has. We dont want to make extensive changes to the original source code of
these applications, since we feel this would defeat the main purpose of a
simulator.In this scenario, we have a few questions, and we shall be really
obliged if somebody, maybe Mr Victor himself (if he has some time :) )
could answer for us, since we are not able to figure out ..
1. Each group of application would have a few tasks in it. some would fit
in the real - time category, while others would fit in the non - realtime
category.. some would be the support functions required by both kind of
tasks.. So,
a. How to segregate these real time and non realtime tasks?
b. How to get these tasks use the same set of libraries..
2. Since the code is liberally sprinkled with the 'printf's and other user
- space functions of Linux (which come in the standard, ie, the kernel
space in pSOS - due to their 'everything is kernel' ideology), do we need
to write wrappers for them too, or is there any other way to tackle this ?
also, i think these wrappers would need to implement both user and kernel
space functionality - something of the sort of
#ifdef __KERNEL__
#define printf printk
#endif
Is this approach correct ?
If somebody could please answer these questions, we shall be grateful,
regards,
Sandip Pathya
-- [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/
