Qnet & endianness issue

QNX Newsgroups (Archives) qnx.rtos
1

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

Regards,
Jacek

2

“Jacek Rudnicki” <jacek.rudnicki@quantum.com.pl> wrote in message
news:cucttf$omo$1@inn.qnx.com…

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Regards,
Jacek

3

Mario Charest postmaster@127.0.0.1 wrote:

“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …
Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

4

“David Gibbs” <dagibbs@qnx.com> wrote in message
news:cud8fo$2oh$2@inn.qnx.com…

Mario Charest postmaster@127.0.0.1 wrote:

“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …
Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

5

Mario Charest wrote:

“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …

Mario Charest postmaster@127.0.0.1 wrote:


“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.


I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

Well, there is an fs-cifs for powerpc…

cheers,

Kris

6

“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:cudhh0$9m0$1@inn.qnx.com…

Mario Charest wrote:
“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …

Mario Charest postmaster@127.0.0.1 wrote:


“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.


I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

Well, there is an fs-cifs for powerpc…

That only works from PowerPC to Workstation and the other way around is
usually easier to deal with.

cheers,

Kris

7

Mario Charest postmaster@127.0.0.1 wrote:

“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:

“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …
Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

8

U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:

“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:

“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …
Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.

That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Host of workstation doesn’t matter.

Thank’s,
Jacek

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

9

Jacek Rudnicki wrote:

U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:


“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …

Mario Charest postmaster@127.0.0.1 wrote:


“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.


That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Host of workstation doesn’t matter.

Use PVM for synchronous and asynchronous message passing between
differet host systems … endianness isn’t an issue with PVM.

See http://www.sf.net/projects/openqnx → PVM

Armin


Thank’s,
Jacek


-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

10

Uzytkownik “Armin Steinhoff” <a-steinhoff@web.de> napisal w wiadomosci
news:cuff02$nkt$1@inn.qnx.com…

Jacek Rudnicki wrote:
U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:


“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …

Mario Charest postmaster@127.0.0.1 wrote:


“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …

Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.


That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Host of workstation doesn’t matter.

Use PVM for synchronous and asynchronous message passing between differet
host systems … endianness isn’t an issue with PVM.

See > http://www.sf.net/projects/openqnx > → PVM

Armin

Hi Armin,

there are several applications under the PVM project.
Can I use PIOUS just for copying purpose?
Should I create PVM cluster first?

Can you share a more information about this?

Thank you,
Jacek

Thank’s,
Jacek


-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

11

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.

That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Nowadays I use the target file system navigator to do this, cause
there isn’t an easy Windows to target solution.

For any other host O.S., I’d export my QNX filesystem for NFS,
and NFS mount it. All the Unix-like ones NFS mount things
pretty easily.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

12

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

The problem is not actually Qnet. Qnet supports this just fine, after
all, the PPC node’s name actually appeared in /net, didn’t it?

The problem is in the resource manager framework. Qnet actually supports
talking to big and little endian machines, but none of the resmgr “drivers”
from QSS handle it. Qnet is endian-agnostic as far as I know.

To a great extent dealing with cross-endian networking requires a fair
amount of dilligence on the developer. Since QNX IPC (and Qnet) do not
examine the message payload in any way, the developer must take care that
their app manages endian-ness within the actual messages themselves.

The resmgr framework CAN handle this, specifically, the dispatch_handler()
function can have an option of MSG_FLAG_CROSS_ENDIAN set, although none of
the QSS provided ones do this. So that means that you can’t walk the
pathspace on a remote node since procnto and the filesystem drivers don’t
set this flag and reject message from “non-native” endian systems.
You can set up a mechanism using the TCP/IP stack to provide you with the
appropriate channel information for your own resmgr that does set the
cross-endian flag, and then you should be able to open a channel and use
native Qnet to talk to that resmgr.

You’ll have to ensure that any non-string/non-byte data is converted to
a consistent endian-ness, which probably means network byte order. This
can make processing and preparing the actual Qnet messages more of a
chore, but nothing that a typical TCP/IP app wouldn’t have to do anyway.

It really is a shame that QSS never went to the effort of making their
stuff support this. At the very least, if they had included support for
this in the message interface to procnto, then you’d at least be able to
open() a channel to the appropriate pathspace for resmgrs.

Cheers,
Camz.

\

Martin Zimmerman camz@passageway.com
Camz Software Enterprises www.passageway.com/camz/qnx/
QNX Programming & Consulting www.qnxzone.com

13

I agree with Martin. It would be nice if we could still find/connect with
resmgrs or other qnx processes over qnet of machines of different endianess.
We programmers can take care of x-endian issues, but please make it possible
for us to at least find and open a channel using qnet.

Kevin


<camz@passageway.com> wrote in message news:cug41c$9fu$1@inn.qnx.com…

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote:
I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

The problem is not actually Qnet. Qnet supports this just fine, after
all, the PPC node’s name actually appeared in /net, didn’t it?

The problem is in the resource manager framework. Qnet actually supports
talking to big and little endian machines, but none of the resmgr
“drivers”
from QSS handle it. Qnet is endian-agnostic as far as I know.

To a great extent dealing with cross-endian networking requires a fair
amount of dilligence on the developer. Since QNX IPC (and Qnet) do not
examine the message payload in any way, the developer must take care that
their app manages endian-ness within the actual messages themselves.

The resmgr framework CAN handle this, specifically, the
dispatch_handler()
function can have an option of MSG_FLAG_CROSS_ENDIAN set, although none of
the QSS provided ones do this. So that means that you can’t walk the
pathspace on a remote node since procnto and the filesystem drivers don’t
set this flag and reject message from “non-native” endian systems.
You can set up a mechanism using the TCP/IP stack to provide you with the
appropriate channel information for your own resmgr that does set the
cross-endian flag, and then you should be able to open a channel and use
native Qnet to talk to that resmgr.

You’ll have to ensure that any non-string/non-byte data is converted to
a consistent endian-ness, which probably means network byte order. This
can make processing and preparing the actual Qnet messages more of a
chore, but nothing that a typical TCP/IP app wouldn’t have to do anyway.

It really is a shame that QSS never went to the effort of making their
stuff support this. At the very least, if they had included support for
this in the message interface to procnto, then you’d at least be able to
open() a channel to the appropriate pathspace for resmgrs.

Cheers,
Camz.

\

Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

14

Jacek Rudnicki wrote:
[clip…]

Use PVM for synchronous and asynchronous message passing between
different host systems … endianness isn’t an issue with PVM.

See > http://www.sf.net/projects/openqnx > → PVM

[clip…]

Can you share a more information about this?

Hi Jacek,

for more PVM info (Parallel Virtual Machine for PC-based Open Control
Systems) have a look to:

SCI Conference Orlando,FL USA
http://www.steinhoff-automation.com/Steinhoff_PVM_SCI2001_e.pdf ENGLISH

Regards,
Jutta

15

Uzytkownik “David Gibbs” <dagibbs@qnx.com> napisal w wiadomosci
news:cuft5v$493$1@inn.qnx.com…

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote:
U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup
on
windows.

I figured if he was talking QNET, he was QNX to QNX.

That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Nowadays I use the target file system navigator to do this, cause
there isn’t an easy Windows to target solution.

For any other host O.S., I’d export my QNX filesystem for NFS,
and NFS mount it. All the Unix-like ones NFS mount things
pretty easily.

NFS solution works fine for me too.

Thank’s
Jacek


-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

16

Hi Jutta,

I will look into these materials soon.

Best,
Jacek

Uzytkownik “Jutta Steinhoff” <j-steinhoff@web.de> napisal w wiadomosci
news:cug603$ajj$1@inn.qnx.com…

Jacek Rudnicki wrote:
[clip…]

Use PVM for synchronous and asynchronous message passing between
different host systems … endianness isn’t an issue with PVM.

See > http://www.sf.net/projects/openqnx > → PVM

[clip…]

Can you share a more information about this?


Hi Jacek,

for more PVM info (Parallel Virtual Machine for PC-based Open Control
Systems) have a look to:

SCI Conference Orlando,FL USA
http://www.steinhoff-automation.com/Steinhoff_PVM_SCI2001_e.pdf > ENGLISH

Regards,
Jutta

17

Uzytkownik “David Gibbs” <dagibbs@qnx.com> napisal w wiadomosci
news:cuft5v$493$1@inn.qnx.com…

Nowadays I use the target file system navigator to do this, cause
there isn’t an easy Windows to target solution.

Is target file system navigator copying routine
equal to the QNX ‘cp’ command?

Can I use this method for transfering flash file system
sockets/partitions (/dev/fs0, /dev/fs0p0 files) ?

Jacek

18

Jacek Rudnicki wrote:

Uzytkownik “Armin Steinhoff” <> a-steinhoff@web.de> > napisal w wiadomosci
news:cuff02$nkt$> 1@inn.qnx.com> …

Jacek Rudnicki wrote:

U¿ytkownik “David Gibbs” <> dagibbs@qnx.com> > napisa³ w wiadomo¶ci
news:cuds0j$gt6$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:



“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cud8fo$2oh$> 2@inn.qnx.com> …


Mario Charest postmaster@127.0.0.1 wrote:



“Jacek Rudnicki” <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cucttf$omo$> 1@inn.qnx.com> …


Hi,

I would like to connect my workstation with PowerPC
target and copy some data between them.

Is it possible to do that?
Or maybe cross endian transmition via qnet is still not
supported?

It’s not, you need to use TCP based services to do that.

Yup. NFS is probably you’re best bet.

I wonder if samba would port easy on PowerPC, NFS is a bitch to setup on
windows.

I figured if he was talking QNET, he was QNX to QNX.


That would be the best and most user friendly solution.
First thread about the “cross endian” issue was sent in 2001.
It was long time ago and as we see this option is still not supported.

Is there any chance to see that Qnet feature in the close future?

Now I’m changing my requirements into a one-way transmition
workstation → target. I would like just copy some files to my
target board. What is the easiest way to do that?

Host of workstation doesn’t matter.

Use PVM for synchronous and asynchronous message passing between differet
host systems … endianness isn’t an issue with PVM.

See > http://www.sf.net/projects/openqnx > → PVM

Armin


Hi Armin,

there are several applications under the PVM project.
Can I use PIOUS just for copying purpose?
Should I create PVM cluster first?

Yes, you should create the PVM cluster at first, because PIOUS is based
on PVM.

Regards

Armin

Can you share a more information about this?

Thank you,
Jacek


Thank’s,
Jacek



-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

19

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

Uzytkownik “David Gibbs” <> dagibbs@qnx.com> > napisal w wiadomosci
news:cuft5v$493$> 1@inn.qnx.com> …
Nowadays I use the target file system navigator to do this, cause
there isn’t an easy Windows to target solution.

Is target file system navigator copying routine
equal to the QNX ‘cp’ command?

I don’t know what qconn actually does for the transfer on the
remote side – I’d assume it is open/read/write, though.

On the windows side, though, it is drag & drop or cut & paste.

Can I use this method for transfering flash file system
sockets/partitions (/dev/fs0, /dev/fs0p0 files) ?

I’ve never actually tried that, so I don’t know.

It might work – or you might have to copy it to some temporary
storage (if you have enough RAM, /dev/shmem), then run cp through
a telnet/terminal/from double-clicking it in the Target Filesystem
Navigator to do the actual remote copy to the special device.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com