Преглед изворни кода

Use FPGA-specific section names, otherwise doxygen is lost

Samuel Thibault пре 5 година
родитељ
комит
f1940a4bb9
1 измењених фајлова са 3 додато и 3 уклоњено
  1. 3 3
      doc/doxygen/chapters/440_fpga_support.doxy

+ 3 - 3
doc/doxygen/chapters/440_fpga_support.doxy

@@ -42,7 +42,7 @@ struct starpu_codelet cl =
 }
 \endverbatim
 
-\subsection Example StarPU/FPGA Application
+\subsection FPGAExample StarPU/FPGA Application
 
 To give you an idea of the interface that we used to exchange data between <c>host</c> (CPU) and <c>FPGA</c> (DFE), here is an example, based on one of the examples of Maxeler (https://trac.version.fz-juelich.de/reconfigurable/wiki/Public). 
 <c>StreamFMAKernel.maxj</c> represents the Java kernel code; it implements a very simple kernel (c=a+b), and <c>Test.c</c> starts it from the <c>fpga_add</c> function; it first sets streaming up from the CPU pointers, triggers execution and waits for the result. The API to interact with DFEs is called <c>SLiC</c> which then also involves the <c> MaxelerOS</c> runtime.
@@ -212,7 +212,7 @@ In the <c>main</c> function, there are four important steps:
 - Free actions.
 - Unload and deallocate the DFE.
 
-\subsection Configuration FPGA Configuration
+\subsection FPGAConfiguration FPGA Configuration
 
 To configure StarPU with FPGA accelerators, we can enable <c>FPGA</c> through the \c configure option <b>"--with-fpga"</b>.
 
@@ -223,7 +223,7 @@ $ make install
 \endverbatim
 
 
-\subsection Launchingprograms  Launching Programs: Simulation
+\subsection FPGALaunchingprograms  Launching Programs: Simulation
 
 Maxeler provides a simple tutorial to use MaxCompiler (https://trac.version.fz-juelich.de/reconfigurable/wiki/Public). Running the Java program to generate maxfile and slic headers (hardware) on Maxeler's DFE device, takes a VERY long time, approx. 2 hours even for this very small example. That's why we use the simulation.