Changes between Version 43 and Version 44 of Writing Rules/Tlmt

Timestamp:

Feb 19, 2008, 9:47:19 PM (16 years ago)

Author:

fpecheux

Comment:

--

Writing Rules/Tlmt

@@ -70 +70 @@
 == C.2) Receiving a VCI response packet ==
 
-To receive a VCI response packet, a call-back function must be defined as a member function of the class '''my_initiator'''. This call-back function (named '''rspReceived()''' in the example), will be executed each time a VCI response packet is received on the '''p_vci''' port. The function name is not constrained, but the arguments must respect the following prototype:
-{{{
-void  rspReceived(vci_rsp_t  *rsp, uint32_t  time)
+To receive a VCI response packet, a call-back function must be defined as a member function of the class '''!VciSimpleInitiator'''. This call-back function (named '''rspReceived()''' in the example), is executed each time a VCI response packet is received on the '''p_vci''' port. The function name is not constrained, but the arguments must respect the following prototype:
+{{{
+tmpl(tlmt_core::tlmt_return&)::callback(soclib::tlmt::vci_rsp_packet<vci_param> *pkt,
+            const tlmt_core::tlmt_time &time,
+            void *private_data)
 }}}
 
 The informations transported by a VCI response packet are defined below:
 {{{
-class vci_rsp_t {
-vci_command_t  cmd;  // VCI transaction type
-uint32_t  length;  // number of words in the packet
-uint32_t  error;  // error code (0 if no error)
-uint32_t  srcid;  // VCI Source ID
-uint32_t  trdid;  // VCI Thread ID
-uint32_t  pktid;  // VCI Packet ID
-}
-}}}
-
-The actions executed by the call-back function depend on the transaction type ('''cmd'''  field), as well as the '''pktid''' and '''trdid''' fields.
+template<typename vci_param>
+class vci_rsp_packet
+{
+public:
+        typename vci_param::cmd_t cmd;    // VCI transaction type
+        size_t length;                    // number of words in the packet
+        uint32_t error;                   // error code (0 if no error)
+        uint32_t srcid;                   // VCI Source ID
+        uint32_t trdid;                   // VCI Thread ID
+        uint32_t pktid;                   // VCI Packet ID
+};
+}}}
+
+The actions executed by the call-back function depend on the response transaction type ('''cmd''' field), as well as the '''pktid''' and '''trdid''' fields.
 
 In the proposed example :
@@ -95 +100 @@
 == C.3) Initiator Constructor ==
 
-The constructor of the class '''my_initiator''' must initialize all the member variables, including the '''p_vci''' port. The '''rspReceived()''' call-back function being executed in the context of the thread sending the response packet, a link between the '''p_vci''' port and the call-back function must be established. Moreover, the '''p_vci''' port must contain a pointer to the initiator local time.
-
-The '''!VciInitiatorPort''' constructor must be called with the following arguments:
-{{{
-p_vci(“vci”, this, &my_initiator::rspReceived, &m_time);
+The constructor of the class '''!VciSimpleInitiator''' must initialize all the member variables, including the '''p_vci''' port. The '''rspReceived()''' call-back function being executed in the context of the thread sending the response packet, a link between the '''p_vci''' port and the call-back function must be established. Moreover, the '''p_vci''' port must contain a pointer to the initiator thread context '''c0'''.
+
+The '''!VciInitiator''' constructor must be called with the following arguments:
+{{{
+p_vci("vci", new tlmt_core::tlmt_callback<VciSimpleInitiator,soclib::tlmt::vci_rsp_packet<vci_param> *>(
+                                         this, &VciSimpleInitiator<vci_param>::rspReceived), &c0)
 }}}