[bootlin/training-materials updates] master: labs/kernel-serial-output: adjust explanation about user-space ioctl programs (6a78a9cb)

[Thomas Petazzoni]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/6a78a9cb9b724cb3f5ccbff33bb73064b780bf49

>---------------------------------------------------------------

commit 6a78a9cb9b724cb3f5ccbff33bb73064b780bf49
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Thu Oct 15 14:29:28 2020 +0200

    labs/kernel-serial-output: adjust explanation about user-space ioctl programs
    
    The serial-get-counter and serial-reset-counter programs no longer
    hardcode the device file path: it can be passed as an argument (see
    commit 43f7cdf3019c7c25eba8eb76675146c349767da2). Adjust the
    explanations accordingly.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


>---------------------------------------------------------------

6a78a9cb9b724cb3f5ccbff33bb73064b780bf49
 labs/kernel-serial-output/kernel-serial-output.tex | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/labs/kernel-serial-output/kernel-serial-output.tex b/labs/kernel-serial-output/kernel-serial-output.tex
index d81a08a2..fa431d3b 100644
--- a/labs/kernel-serial-output/kernel-serial-output.tex
+++ b/labs/kernel-serial-output/kernel-serial-output.tex
@@ -187,11 +187,12 @@ Two test applications (in source format) are already available in the
 They assume that \code{SERIAL_RESET_COUNTER} is ioctl operation \code{0}
 and that \code{SERIAL_GET_COUNTER} is ioctl operation \code{1}.
 
-Modify their source code according to the exact name of the device file
-you wish to use, and compile them on your host:
+Compile them:
 
 \begin{verbatim}
 arm-linux-gnueabi-gcc -static -o serial-get-counter serial-get-counter.c
+arm-linux-gnueabi-gcc -static -o serial-reset-counter serial-reset-counter.c
 \end{verbatim}
 
-The new executables are then ready to run on your target.
+The new executables are then ready to run on your target. They take as
+argument the path to the device file corresponding to your UART.