[bootlin/training-materials updates] master: labs/sysdev-accessing-hardware: improve explanation about libgpiod (9f552ec8)

[Thomas Petazzoni]

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

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

commit 9f552ec897ab055ee0cdbd7e8bf4a50cc7d1c58d
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Thu Sep 22 16:43:28 2022 +0200

    labs/sysdev-accessing-hardware: improve explanation about libgpiod
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


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

9f552ec897ab055ee0cdbd7e8bf4a50cc7d1c58d
 labs/sysdev-accessing-hardware/sysdev-accessing-hardware.tex | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/labs/sysdev-accessing-hardware/sysdev-accessing-hardware.tex b/labs/sysdev-accessing-hardware/sysdev-accessing-hardware.tex
index 691bbe6c..acc56cfb 100644
--- a/labs/sysdev-accessing-hardware/sysdev-accessing-hardware.tex
+++ b/labs/sysdev-accessing-hardware/sysdev-accessing-hardware.tex
@@ -95,9 +95,12 @@ and asking questions to your instructor.
 \section{Driving GPIOs}
 
 At this stage, we can only explore GPIOs through the legacy interface
-in \code{/sys/class/gpio}, because the {\em libgpiod} interface commands
-are not supported in BusyBox yet. We will later be able to compile and
-use such commands.
+in \code{/sys/class/gpio}, because the {\em libgpiod} interface
+commands are provided through a dedicated project which we have to
+build separately, and {\em Busybox} does not provide a
+re-implementation for the {\em libgpiod} tools. In a later lab, we
+will build {\em libgpiod} tools which use the modern
+\code{/dev/gpiochipX} interface.
 
 The first thing to do is to enable this legacy interface by enabling
 \kconfig{CONFIG_GPIO_SYSFS} in the kernel configuration. Also make sure