Re: [tipc-discussion] port name - port_id ?

2008-02-25 Thread Stephens, Allan
11:36 AM To: Stephens, Allan Cc: tipc-discussion@lists.sourceforge.net Subject: Re: [tipc-discussion] port name - port_id ? On Freitag 22 Februar 2008, Stephens, Allan wrote: The Linux 2.6.24 kernel contains TIPC 1.6.2 code. Oh, that old... Any chance for pushing something newer into the mainline

Re: [tipc-discussion] port name - port_id ?

2008-02-25 Thread Erich Focht
Hi Al, On Montag 25 Februar 2008, Stephens, Allan wrote: Erich, is it possible for you to upgrade to TIPC 1.7.5? yes, I will try. Not sure I can do it today, though (I'm in CET timezone). Thanks, Erich - This SF.net email

Re: [tipc-discussion] port name - port_id ?

2008-02-25 Thread Horvath, Elmer
]; Horvath, Elmer Cc: tipc-discussion@lists.sourceforge.net Subject: RE: [tipc-discussion] port name - port_id ? Hi guys: Since Erich is using TIPC 1.6.2, I wonder if he's running into a native API problem Elmer discovered and which is fixed in TIPC 1.7.5. I think it had something to do

Re: [tipc-discussion] port name - port_id ?

2008-02-23 Thread Erich Focht
Hello, by the way, I added a conn_error_callback, as in your code. Interestingly: after sending the empty tipc_send2name the conn_error_cb gets invoked with reason=2. The tipc_send fails and returns something like -22 or -28, so I let the module loading fail. If instead I send directly the

[tipc-discussion] port name - port_id ?

2008-02-22 Thread Erich Focht
Hello, with the native interface I'd like to do (inside a kernel module): tipc_connect2port(myref, subscr_service); I know the target port name {1, 1} but how can I get the port_id, which is required as argument to tipc_connect2port? The function tipc_nametbl_translate isn't exported...

Re: [tipc-discussion] port name - port_id ?

2008-02-22 Thread Horvath, Elmer
PM To: tipc-discussion@lists.sourceforge.net Subject: [tipc-discussion] port name - port_id ? Hello, with the native interface I'd like to do (inside a kernel module): tipc_connect2port(myref, subscr_service); I know the target port name {1, 1} but how can I get the port_id, which

Re: [tipc-discussion] port name - port_id ?

2008-02-22 Thread Jon Maloy
To: Stephens, Allan Cc: tipc-discussion@lists.sourceforge.net Subject: Re: [tipc-discussion] port name - port_id ? Hi Allan, sorry, just saw your reply. Actually I was sending my subscription info in the first send2name, but none of the callbacks gets alive. You say I should at least get an empty

Re: [tipc-discussion] port name - port_id ?

2008-02-22 Thread Stephens, Allan
Hi Erich: The Linux 2.6.24 kernel contains TIPC 1.6.2 code. -- Al -Original Message- From: Erich Focht [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:30 PM To: Stephens, Allan Cc: tipc-discussion@lists.sourceforge.net Subject: Re: [tipc-discussion] port name - port_id

Re: [tipc-discussion] port name - port_id ?

2008-02-22 Thread Horvath, Elmer
Of Erich Focht Sent: Friday, February 22, 2008 1:22 PM To: Horvath, Elmer Cc: tipc-discussion@lists.sourceforge.net Subject: Re: [tipc-discussion] port name - port_id ? Dear Elmer, thanks for your reply. I roughly know how to deal with the port ref in a callback. My problem is: I'd like to use