Porting PSOS code

QNX Newsgroups (Archives) qdn.public.porting
1

Hi all

Some lazer control chaps are considering a port from PSOS to RtP.

Has anyone ported some PSOS code?

Any real snags?

Rob

2

Robert Cameron <robertc@symmetry.com.au> wrote:

Hi all

Some lazer control chaps are considering a port from PSOS to RtP.

Has anyone ported some PSOS code?

I just taught a group who were porting PSOS code. I don’t know about
snags – but there is a real difference in model.

PSOS doesn’t have any clear idea of a process as QNX uses them, nor,
really, threads, though they have something like that.

It seems (from what they said) that PSOS has “tasks” which seem to be
a combination of a sequence of code being executed [thread(s)], some data
and some functions – but you can call one tasks’ functions from within
another task. Everything shares the same data/address space – so anyone
can see anyone’s data and use it as needed/wanted. This may cause some
problems in porting if the code is written to do this. Also, they will
have to re-arrange their thinking – if at least some of them have a
background in Unix or other OS with a process model, this will really
help.

-David

3

I did some Psos a long time ago, the main difference I remember is
there is no virtual memory ( matching David’s description).
It just like one big process with threads, could be easier to port it as
such,
but ugly :wink:

“David Gibbs” <dagibbs@qnx.com> wrote in message
news:8vm4kr$k9d$1@nntp.qnx.com…

Robert Cameron <> robertc@symmetry.com.au> > wrote:
Hi all

Some lazer control chaps are considering a port from PSOS to RtP.

Has anyone ported some PSOS code?

I just taught a group who were porting PSOS code. I don’t know about
snags – but there is a real difference in model.

PSOS doesn’t have any clear idea of a process as QNX uses them, nor,
really, threads, though they have something like that.

It seems (from what they said) that PSOS has “tasks” which seem to be
a combination of a sequence of code being executed [thread(s)], some data
and some functions – but you can call one tasks’ functions from within
another task. Everything shares the same data/address space – so anyone
can see anyone’s data and use it as needed/wanted. This may cause some
problems in porting if the code is written to do this. Also, they will
have to re-arrange their thinking – if at least some of them have a
background in Unix or other OS with a process model, this will really
help.

-David

4

You migth take a look at http://www.mvista.com/psos2linux/index.html

Dmitri

Robert Cameron wrote:

Hi all

Some lazer control chaps are considering a port from PSOS to RtP.

Has anyone ported some PSOS code?

Any real snags?

Rob