[bootlin/training-materials updates] master: labs/kernel-serial-output: a few more things to look at in sysfs (9af12bf8)

[Thomas Petazzoni]

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

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

commit 9af12bf8cc8d06081561d8735d6fa8b213feaf68
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Thu Jun 4 08:10:17 2020 +0200

    labs/kernel-serial-output: a few more things to look at in sysfs
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


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

9af12bf8cc8d06081561d8735d6fa8b213feaf68
 labs/kernel-serial-output/kernel-serial-output.tex | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/labs/kernel-serial-output/kernel-serial-output.tex b/labs/kernel-serial-output/kernel-serial-output.tex
index 04b47a0d..d81a08a2 100644
--- a/labs/kernel-serial-output/kernel-serial-output.tex
+++ b/labs/kernel-serial-output/kernel-serial-output.tex
@@ -85,6 +85,12 @@ At this stage, make sure you can load and unload the driver multiple
 times. This should reveal registration and deregistration issues if
 there are any.
 
+Check in \code{/sys/class/misc} for an entry corresponding to the
+registered devices, and within those directories, check what the
+\code{device} symbolic link is pointed to. Check the contents of the
+\code{dev} file as well, and compare it with the major/minor number of
+the device nodes created in \code{/dev} for your devices.
+
 \section{Implement the write() routine}
 
 Now, add code to your write function, to copy user data to the serial