Changes between Version 23 and Version 24 of Writing Rules/Caba

Timestamp:

Apr 8, 2009, 2:34:53 PM (16 years ago)

Author:

Nicolas Pouillon

Comment:

Fix links

Writing Rules/Caba

@@ -44 +44 @@
 Any SoCLib hardware components having a VCI interface is called a ''VCI component'', and must include 
 at least one of the the two following files, defining the VCI advanced ports :
- * [source:trunk/soclib/systemc/include/caba/interface/vci_target.h caba/interface/vci_target.h]
- * [source:trunk/soclib/systemc/include/caba/interface/vci_initiator.h caba/interface/vci_initiator.h]
-
-As VCI signals can have variable widths, all VCI components must be defined with templates. The [source:trunk/soclib/systemc/include/caba/interface/vci_param.h caba/interface/vci_param.h] file contains the definition of the VCI parameters object. This object must be passed as a template parameter to the component.
+ * [source:trunk/soclib/soclib/communication/vci/caba/source/include/vci_target.h]
+ * [source:trunk/soclib/soclib/communication/vci/caba/source/include/vci_initiator.h]
+
+As VCI signals can have variable widths, all VCI components must be defined with templates. The [source:trunk/soclib/soclib/communication/vci/caba/source/include/vci_param.h] file contains the definition of the VCI parameters object. This object must be passed as a template parameter to the component.
 
 A typical VCI component declaration is:
 {{{
-#include "caba/util/base_module.h"
-#include "caba/interface/vci_target.h"
+#include "base_module.h"
+#include "vci_target.h"
 
 namespace soclib { namespace caba {
@@ -62 +62 @@
 
 };
+
 }}
 }}}
 
 The SystemC top cell defining the system architecture must include the following file, defining the advanced VCI signals :
- * [source:trunk/soclib/systemc/include/caba/interface/vci_signals.h caba/interface/vci_signals.h].
+ * [source:trunk/soclib/soclib/communication/vci/caba/source/include/vci_signals.h].
 
 A SoCLib hardware component that has no VCI interface should use a dedicated VCI  wrapper in order to be connected to the VCI interconnect.
@@ -86 +87 @@
 In order to simplify the memory map definition, and the hardware component configuration, a
 generic object, called ''mapping table'' has been defined in
-[source:trunk/soclib/systemc/include/common/mapping_table.h common/mapping_table.h].
+[source:trunk/soclib/soclib/lib/mapping_table/include/mapping_table.h mapping_table.h].
 This is an associative table of memory segments. Any segment must be allocated to one single
 VCI target. The segment object is defined in
-[source:trunk/soclib/systemc/include/common/segment.h common/segment.h],
+[source:trunk/soclib/soclib/lib/segment/include/segment.h segment.h],
 and contains five attributes:
 {{{
@@ -136 +137 @@
 
 All structural parameters should be be defined as member variables. The values are generally defined by a constructor argument.
-Instance name is stored in [source:trunk/soclib/systemc/include/common/base_module.h soclib::common::BaseModule], inherited by
-[source:trunk/soclib/systemc/include/caba/util/base_module.h soclib::caba::BaseModule].
+Instance name is stored in [source:trunk/soclib/soclib/lib/base_module/include/base_module.h soclib::common::BaseModule], inherited by
+[source:trunk/soclib/soclib/lib/base_module/include/caba/caba_base_module.h soclib::caba::BaseModule].
 For example, a VCI target will contain a reference to the the assigned segment, in order to check
 possible segmentation errors during execution.
@@ -150 +151 @@
 a VCI index. Moreover, generic simulation models can have structural parameters. The parameter
 values must be defined as constructor arguments, and used by the constructor to configure the hardware ressources. A constructor  argument frequently
-used is a reference on the [source:trunk/soclib/systemc/include/common/mapping_table.h soclib::common::MappingTable], that defines the segmentation of the system address space.
+used is a reference on the [source:trunk/soclib/soclib/lib/mapping_table/include/mapping_table.h soclib::common::MappingTable], that defines the segmentation of the system address space.
 A typical VCI component will have the following constructor arguments:
 
@@ -201 +202 @@
 == C1) Component definition ==
 
-Let's take the [source:trunk/soclib/systemc/include/caba/target/vci_locks.h soclib::caba::VciLocks]
+Let's take the [source:trunk/soclib/soclib/module/internal_component/vci_locks/caba/source/include/vci_locks.h soclib::caba::VciLocks]
 component definition and comment it.
 
@@ -274 +275 @@
 == C2) Component implementation ==
 
-Here is the [source:trunk/soclib/systemc/src/caba/target/vci_locks.cc soclib::caba::VciLocks] component implementation:
+Here is the [source:trunk/soclib/soclib/module/internal_component/vci_locks/caba/source/src/vci_locks.cc soclib::caba::VciLocks] component implementation:
 
 {{{