Changes between Version 15 and Version 16 of arch_info

Timestamp:

Jan 16, 2017, 10:56:28 AM (7 years ago)

Author:

alain

Comment:

--

arch_info

@@ -98 +98 @@
 || '''size'''        || segment size (bytes) ||
 
-=== 3.4) Peripheral ===
+=== 3.4) Peripherals ===
 
-The '''archi.addPeriph( )''' construct adds one peripheral in a cluster. ALMOS-MK supports multi-channels peripherals.
+The '''archi.addDevive( )''' construct adds one peripheral in a cluster. ALMOS-MK supports multi-channels peripherals.
+ALMOS-MK supports multi-channels peripherals.
 This construct has the following arguments:
 || '''cxy'''         || cluster identifier ||
@@ -106 +107 @@
 || '''size'''        || segment size (bytes) ||
 || '''ptype'''     || Peripheral type ||
-|| '''subtype'''  || Peripheral subtype ||
 || '''channels''' || number of channels for multi-channels peripherals ||
 || '''arg0'''        || optionnal argument depending on peripheral type ||
@@ -113 +113 @@
 || '''arg3'''          || optionnal argument depending on peripheral type ||
 
-Each peripheral type is defines by a composite index (ptype,subtype).
-The supported peripheral types and subtypes are defined in the [source:almos-work/tools/python/genarch.py genarch.py] file.
+The peripheral type defines actually a composite index containing a functional type (func-type), and an implementation type (impl_type).
+The supported peripheral types are defined in the [source:almos-work/tools/arch_info/arch_classes.py arch_classes.py] file.
 
 The following peripheral components require specific arguments with the following semantic:
@@ -124 +124 @@
 || arg3       || unused                             || unused                       || number of STATUS registers       ||
 
-Hardware coprocessors using the Generic DMA controller to access memory are described as peripherals. They must be defined with the MWR ''ptype'' argument, and the ''subtype'' argument defines the coprocessor type. 
+Hardware coprocessors using the Generic DMA controller to access memory are described as peripherals. They must be defined with the MWR ''func_ptype'' argument, and the ''impl_type'' argument defines the coprocessor type. 
 
 === 3.5) Interrupt line ===
 
-The '''archi.addIrq()''' is used to describe the hardware interrupts routing from a physical peripheral to an interrupt concentrator. This construct adds one input IRQ line to an XCU peripheral, or to a PIC peripheral. It has the following arguments:
-|| '''periph'''   || peripheral receiving the IRQ line ||
-|| '''index'''    || input port index ||
-|| '''isrtype'''  || Interrupt Service Routine type ||
-|| '''channel''' || channel index for multi-channel ISR ||
+The '''archi.addIrq()''' construct is used to describe the hardware interrupts routing from an output interrupt port in a physical peripheral, to an input interrupt port in an interrupt concentrator. This construct adds one input IRQ line to an XCU peripheral, or to a PIC peripheral. It has the following arguments:
+|| '''dst_dev'''   || destination device (XCU or PIC)  ||
+|| '''index'''    || input port index in destination device ||
+|| '''src_dev'''  || source device ||
+|| '''channel'''  || source device channel (default value is 0) ||
+|| '''is_rx''' || source device direction (default value is False) ||
 
-The supported ISR types are defined in the [source:almos-work/tools/python/genarch.py genarch.py] file.
+The supported devices types are defined in the [source:almos-work/tools/arch_info/arch_class.py arch_class.py] file.
 
 
@@ -142 +143 @@
 Therefore, the '''boot_info_t''' structure defines the generic (hardware independent) interface between the hardware specific boot-loader and the kernel.  
 
-It is defined in the [source:almos-work/tools/archinfo/boot_info.h boot_info.h] file. 
+It is defined in the [source:almos-work/tools/arch_info/boot_info.h boot_info.h] file.