[bootlin/training-materials updates] master: slides/sysdev-flash-filesystems: clarify what raw flash is (2d3cb327)

[Michael Opdenacker]

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

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

commit 2d3cb3273115ecdf0e52c5d4c724246b6ddb7750
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Jan 20 19:19:22 2023 +0100

    slides/sysdev-flash-filesystems: clarify what raw flash is
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

2d3cb3273115ecdf0e52c5d4c724246b6ddb7750
 slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index da5ecc3a..20d5bb8d 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -14,8 +14,10 @@
     \end{itemize}
   \item Raw flash devices:
     \begin{itemize}
-    \item Allow for random data access too
-    \item Require erasing before writing on the media
+    \item Flash chips directly driven by the flash controller on your SoC.
+          You can control how they are managed.
+    \item Allow for random data access too, but require erasing before
+          writing on the media.
     \item Read and write block size (for example 4 KiB) don't use
           the same block size as erasing (for example 128 KiB).
     \item Multiple flash technologies: NOR flash, NAND