Javier Barreiro <jbarreiro@vai-ingdesi.com> wrote:
I replied in the .qnx2 newsgroup, not knowing this had been posted
and replied to here, as well.
āRennie Allenā <> rgallen@attbi.com> > wrote in message
news:bfiaug$cqs$> 1@inn.qnx.com> ā¦
Javier Barreiro wrote:
attach_port and signal_hw_port (IIRC) would loosely translate to pulses (I
programmed extensively in QNX2 but my neural net LRU cache algorithm has
tossed
probably 95% of that stuff).
I didnāt undestard how i can replace that functions, as i am not sure what
they exactly do. What do you mean with translate to pulses?
Do you have the help (syntax and parameters) of these functions for QNX? Or
in other case, where do you think that i could find it.
Read the IPC section of the system architecture manual. This one will not
be a simple replacement ā there will be extras.
Depending on the setup, though, it may actually be simpler.
signal(port) will probably become: MsgSendPulse() or MsgDeliverEvent()
depending on direction. (client->server and server->client respectively).
name_attach()/name_open() may do all the setup needed for the client->server
side.
For server->client, you will also likely need ChannelCreate(), ConnectAttach(),
and SIGEV_PULSE_INIT() (docād under _sigevent structure).
create_seg is unnecessary (QNX6 is 32 bit - whoa that feels weird to say -
as if
anything isnāt 32 bit anymore > > .
In this case i think that create_seg is mapping an IO area to a mem area. Is
it right? Could I replace it with mmap?
Again, if you have the help files for this function, please let me know.
mmap_device_memory(), or mmap(), or mmap64().
For dual-ported RAM or equivalent.
Hey QSSL how about a mig26ā¦ (didnāt think so >
mig24 | mig4nto
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.