[bootlin/training-materials updates] master: sysdev: slides: flash-filesystems: remove ubinize details (4f5be8e4)

Luca Ceresoli luca.ceresoli at bootlin.com
Sat Feb 4 00:35:05 CET 2023

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


commit 4f5be8e44d2c99f5d07d552e2ed664bda6ffdc6a
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Fri Feb 3 18:53:06 2023 +0100

    sysdev: slides: flash-filesystems: remove ubinize details
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


 .../sysdev-flash-filesystems.tex                   | 73 ----------------------
 1 file changed, 73 deletions(-)

diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 9cf3f646..34097339 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -254,79 +254,6 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(XLoader)ro,1536k(UBoot)ro...
-  \frametitle{ubinize: create a UBI image}
-  \small
-  \begin{itemize}
-  \item \code{ubinize} creates a UBI image to be flashed on an MTD partition,
-	from a specification of the contents of its volumes.
-  \item \code{static} volumes are meant to store {\bf read-only} blobs of data,
-	and get the minimum corresponding size. CRC checks are done on
-        them.
-  \item A read-only UBIFS filesystem can go in a \code{static}
-	volume, but in this case \code{dynamic} volumes are best
-        for performance (CRC checking also done at UBIFS level).
-  \item \code{autoresize}: allows to fill all remaining UBI space
-  \item Example configuration file for \code{ubinize}:
-  \end{itemize}
-  \begin{columns}
-  \end{columns}
-  \frametitle{ubinize command line}
-  \begin{itemize}
-  \item \code{ubinize} takes the following arguments:
-    \begin{itemize}
-    \item \code{-o <output-file-path>}\\
-	Path to the output image file
-    \item \code{-p <peb-size>}\\
-	The PEB size (MTD erase block size)
-    \item \code{-m <min-io-size>}\\
-	The minimum write unit size (MTD write size)
-    \item \code{-s <subpage-size>}\\
-	Subpage size, only needed if both your flash and your
-	flash controller are supporting subpage writes
-    \item The last argument is the path to the \code{ubinize}
-	  configuration file
-    \end{itemize}
-  \item Example: \code{ubinize -o ubi.img -p 256KiB -m 4096 -s 2048 ubinize.cfg}
-  \end{itemize}
   \frametitle{Linux: UBI image creation workflow}

More information about the training-materials-updates mailing list