Changes between Version 34 and Version 35 of mapping_info

Timestamp:

Mar 8, 2015, 3:01:26 PM (9 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -4 +4 @@
 
 The GIET_VM bootloader loads the GIET_VM kernel and the user application(s) on the target architecture. 
-All user applications segments (code, data, stack and heap) the kernel code and the critical kernel structures (page tables or processors schedulers) are statically build  by the GIET_VM bootloader, as specified by the mapping directives. 
+All user applications segments (code, data, stack and heap) the kernel code and the critical kernel structures (page tables or processors schedulers), are statically build  by the GIET_VM bootloader, as specified by the mapping directives. 
 
 The main goal of this static approach is to allow the system designer to control the placement of the tasks on the processors, but also to control the placement of software objects on the distributed physical memory banks. It supports replication of (read-only) critical objects such as kernel code, user code, or page tables. The page tables are statically initialized in the boot phase, and are not modified anymore in the execution phase.
@@ -17 +17 @@
 
 1.  It contains a description of the target hardware architecture, with the following constraints: 
- * All hardware components respect the VCI communication protocol.
  * All processor cores are identical (MIPS32). 
  * The clusters form a 2D mesh topology. The mesh size is defined by the (X_SIZE,Y_SIZE) parameters.