Changeset 1028 for branches/reconfiguration

Timestamp:

Dec 20, 2015, 7:32:26 PM (9 years ago)

Author:

cfuguet

Message:

Fixing indentation in the README file

File:

• branches/reconfiguration/platforms/tsar_generic_iob/README (modified) (4 diffs)

branches/reconfiguration/platforms/tsar_generic_iob/README

@@ -10 +10 @@
 directory)
 
-        svn co https://www-soc.lip6.fr/svn/tsar_dist_boot/
+    svn co https://www-soc.lip6.fr/svn/tsar_dist_boot/
 
 
@@ -23 +23 @@
 tsar repo's working directory
 
-        In bash:
+    In bash:
 
-                export TSARPATH=<path_to_tsar>
+        export TSARPATH=<path_to_tsar>
 
-        In tcsh:
+    In tcsh:
 
-                setenv TSARPATH <path_to_tsar>
+        setenv TSARPATH <path_to_tsar>
 
 The TSARPATH environment variable is used by the soclib.conf file in order to
@@ -40 +40 @@
 don't want to have the branches, and the trunk in different working
 directories, you can directly modify the soclib.conf configuration file, and
-add manually the directories. 
+add manually the directories.
 
 
@@ -68 +68 @@
 
   --batch-mode / -b      Framebuffer and TTYs are not shown.
-                         TTYs are redirected to files 
+                         TTYs are redirected to files
 
-  --faulty-router / -fr  Inject a faulty router. The faulty router is 
-                                                 designated by three arguments: T, X, and Y.
-                                                 - T is the index of the target NoC
+  --faulty-router / -fr  Inject a faulty router. The faulty router is
+                         designated by three arguments: T, X, and Y.
+                         - T is the index of the target NoC
                            (CMD:0, RSP:1, M2P:2, P2M:3, CLACK:4).
-                                             - X and Y are the coordinates of the router.
-                                                 You can inject several faulty routers by repeating
+                         - X and Y are the coordinates of the router.
+                         You can inject several faulty routers by repeating
                          the -fr parameter.
-                                                 Example:
+                         Example:
                             Run simulation with a 4x4 mesh, and the routers
                             CMD(3,3) and RSP(3,0) are faulty.
 
-                                                            scripts/onerun -x 4 -y 4 -fr 0 3 3 -fr 1 3 0
-                                                        
+                                scripts/onerun -x 4 -y 4 -fr 0 3 3 -fr 1 3 0
+
   --faulty-core / -fc    Inject a faulty core. The faulty core is
-                                                 designated by three arguments X, Y, and L.
+                         designated by three arguments X, Y, and L.
                          - X, and Y are the global coordinates of the core.
                          - L is the local id of the core
-                                                 You can inject several faulty cores by repeating
+                         You can inject several faulty cores by repeating
                          the -fc parameter.
-                                                 Example:
+                         Example:
                             Run simulation with a 4x4 mesh, and the
-                                                        cores (0,0,0) and (2,3,1) are faulty.
+                            cores (0,0,0) and (2,3,1) are faulty.
 
-                                                            scripts/onerun -x 4 -y 4 -fc 0 0 0 -fc 2 3 1
+                                scripts/onerun -x 4 -y 4 -fc 0 0 0 -fc 2 3 1
 
   --disk-image / -di     Path to the disk image from which the operating system
-                                                 will be loaded at the end of the distributed boot
-                                                 procedure. This disk image is the file handled by the
-                                                 external disk controller.
+                         will be loaded at the end of the distributed boot
+                         procedure. This disk image is the file handled by the
+                         external disk controller.