Hi AL,
Nice to meet you here! Thank you very much for your kindly reply to my
questions!
After last time,I checked TIPC1.0.2 package detailly,then found some
pointer mistakes in usrreq(),it need do some conversion for input
parameter.Till now,my porting version can work as standalone mode in
vxsim.But when I am trying to setup two vxsims to test porting work, it
failed to send message using CLUSTER scope.I don't know what's issue
will affect TIPC working like this?The following is my configuration:
setup two Vxsims to simulate networking,passed ping test.
VxSim0:192.168.255.1
tipc_init("a=1.1.1,be=eth:nt0")
setup a TIPC server in this Vxsim0 using CLUSTER scope
VxSim1:192.168.255.2
tipc_init("a=1.1.2,be=eth:nt0")
setup a TIPC client to send message using CLUSTER scope,but get errors
saying that it failed to send message.
I hope you can give me some hints to continue my work during your spare
time!
Thanks again!
Tyler Han
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Stephens, Allan
Sent: Saturday, January 26, 2008 3:45 AM
To: Han Jian-feng-Q16072
Cc: [email protected]
Subject: Re: [tipc-discussion] Porting TIPC 1.0.2 to VxWorks5.5.1
Hi Tyler:
The VxWorks version of TIPC is designed to work with the network/socket
code used in VxWorks 6.x. I believe that the only version of TIPC that
runs on VxWorks 5.x is a very early version (TIPC 1.0.0, if I recall
correctly) that is included with some of the MSP versions of VxWorks
5.5. These MSP versions of VxWorks use the same network/socket code as
VxWorks 6.0; the general purpose version of VxWorks 5.5 uses earlier
network/socket code, which may explain the issues you are seeing with
VxWorks 5.5.1.
Over the last few years a few people have inquired about the work
involved in porting TIPC to specific VxWorks 5.x releases, but I don't
know of anyone who has actually done so. The effort required is likely
to be significant (i.e. more than just a few days, and could be much
longer).
This seems to leave you with a number of options:
1) Upgrade to VxWorks 6.x, which would allow you to use the best and
most up to date version of TIPC.
2) Upgrade to VxWorks 5.5.1 MSP, which would allow you to use TIPC 1.0
(probably upgradeable to TIPC 1.0.2).
3) Try to port TIPC yourself. (I'm not sure whether you'd be better off
trying to port TIPC 1.7.5 than TIPC 1.0.2).
4) Pay someone to do the port for you. (Wind River has a Professional
Services division that undertakes work of this nature; there may be
other qualified firms too.)
Conflict of interest alert: I am an employee of Wind River (although not
for its Professional Services division).
Regards,
Al
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Han
Jian-feng-Q16072
Sent: Wednesday, January 23, 2008 5:06 AM
To: [email protected]
Subject: [tipc-discussion] Porting TIPC 1.0.2 to VxWorks5.5.1
Dear,all
I am very glad to meet you experts in this mailing list!
My application is based on VxWorks5.5.1,so I try to port earliest
TIPC1.0.2 to Vxworks5.5.1. I find many errors after I modified socket.c
accroding to porting guide, it looks it is not a easy thing to complete
this task. Anyone here has tried this kind of work before?Pls. give
your suggestions!
Thanks! :-)
Tyler Han
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
