Changeset 111

Timestamp:

Feb 8, 2010, 12:22:11 PM (15 years ago)

Author:

coach

Message:

pc

Location:

anr

Files:

• task-4.tex (modified) (3 diffs)
• task-5.tex (modified) (3 diffs)
• task-7.tex (modified) (1 diff)

anr/task-4.tex

@@ -56 +56 @@
     \begin{livrable}
     \itemL{18}{24}{x}{\Stima}{UGH enhancement 1}{0:9:0}
-        The UGH software whith support for treating automatically data dominated sections
+        Release of the UGH software with support for treating automatically data dominated sections
         included into a control dominated application.
     \itemL{21}{27}{x}{\Stima}{UGH enhancement 2}{0:3:6}
-        The UGH software that is able to generate a micro-architecture without the
+        Release of the UGH software able to generate a micro-architecture without the
         variable binding currently done by the designer.
     \itemL{6}{18}{x}{\Subs}{GAUT enhancement 1}{0:0:0}
@@ -78 +78 @@
         Release of the GAUT software that supports the features defined in \ST ????.
     \end{livrable}
-\item In FPGA-SoC, the frequency is given by the processors and the BUS. The coprocessors
+\item In FPGA-SoC, the frequency is given by the processor(s) and the system BUS. The coprocessors
     generated by HLS synthesis must respect this frequency. However, the HLS tools can not
     guarantee that the micro-architectures they generate accurately respect this
     frequency. This is especially the case when the target is a FPGA device, because the
     delays are really known only after the RTL synthesis and that estimated delays used
-    by the HLS are very imprecize. The goal of this \ST is to provide a tool to adapt
+    by the HLS are very inaccurate. The goal of this \ST is to provide a tool that adapts
     the coprocessors frequency to the FPGA-SoC frequency after the coprocessor RTL
     synthesis.
@@ -93 +93 @@
     \itemL{24}{33}{x}{\Supmc}{frequency calibration}{2:.5:3.5}
         The frequency calibration software consists of a driver in the FPGA-SoC operating
-        system and of a control software on a PC.
+        system and of a control software on a PC. %FIXME == {Pas clair pour le HPC. Comprends pas}
     \end{livrable}
 \end{workpackage}

anr/task-5.tex

@@ -12 +12 @@
 figures~\ref{coach-flow} and \ref{archi-hpc}. It consists in
 \begin{itemize}
-\item Helping the HPC designer to find a good partition of the initial application
+\item Providing a software tool that helps the HPC designer to find a good partition of the initial application
     (figure~\ref{archi-hpc}).
 \item Providing communication schemes between the software part running on the PC and the
-FPGA-SoC.
+FPGA-SoC. %FIXME = {Quelle difference avec l'item qui suit ???}
 \item Implementing the communication scheme at all levels: partition help, software
 implementation both on the PC and in the operating system of the FPGA-SoC, hardware.
@@ -25 +25 @@
 transfers. The reasons of this choices are that both ALTERA and Xilinx provide PCI/X IP for
 their FPGA and that GPU HPC softwares use also it.
-This will allow us at least to be inspired by GPU communication schemes and may be to reuse
-parts of the GPU softwares.
+%FIXME == {ai supprime (mis en commentaire) la phrse qui suivait}
+%This will allow us at least to be inspired by GPU communication schemes and may be to reuse
+%parts of the GPU softwares.
 
 \end{objectif}
 %
+%FIXME == {Ne doit onpas fusionner les taches ST6-1, ST6-2, ST6-3 et pourquoi pas ST6-4 ???}
 \begin{workpackage}
 \item This \ST is the definition of the communication schemes as a software API
@@ -37 +39 @@
     \itemL{0}{6}{d}{\Supmc}{HPC communication API}{1.0:0:0}
         \setMacroInAuxFile{hpcCommApi}
-        User reference manual describing the API.
+        Specification describing the API.
     \end{livrable}
 \item This \ST consists in helping to partition applications.

anr/task-7.tex

@@ -31 +31 @@
         adding, suppressing, replacing pages).
         Especialy the user reference manuals provided in the other tasks will be published
-        in this site. The published articles will be also be installed in this site.
+        on this site. The published articles will be also be installed in this site.
       \itemL{6}{36}{}{\Supmc}{release handling}{1:.5:.5}
         This deliverable deals with the elaboration of the COACH software milestones and