From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/3] Documentation: user: booting-linux: split off mtdparts fixup section
Date: Tue, 5 May 2026 11:50:59 +0200 [thread overview]
Message-ID: <20260505095137.1123867-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20260505095137.1123867-1-a.fatoum@pengutronix.de>
Specifying mtdparts on the command line instead of the device tree is
not as relevant nowadays, so move it into its own section at the end as
not to clutter the more relevant global.linux.bootargs section that is
going to be extended in a later commit.
While at it, extend it to cover the related blkdevparts as well.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/user/booting-linux.rst | 55 +++++++++++++++-------------
1 file changed, 30 insertions(+), 25 deletions(-)
diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 3972777f30cf..cc0bdb4661ca 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -98,31 +98,6 @@ with ``global.linux.bootargs.`` will be concatenated to the bootargs:
Kernel command line: console=ttymxc0,115200n8 earlyprintk ignore_loglevel
-Additionally all variables starting with ``global.linux.mtdparts.`` are concatenated
-to a ``mtdparts=`` parameter to the kernel. This makes it possible to consistently
-partition devices with the :ref:`command_addpart` command and pass the same string as used
-with addpart to the Kernel:
-
-.. code-block:: sh
-
- norparts="512k(bootloader),512k(env),4M(kernel),-(root)"
- nandparts="1M(bootloader),1M(env),4M(kernel),-(root)"
-
- global linux.mtdparts.nor0="physmap-flash.0:$norparts"
- global linux.mtdparts.nand0="mxc_nand:$nandparts"
-
- addpart /dev/nor0 $norparts
- addpart /dev/nand0 $nandparts
-
- ...
-
- bootm zImage
-
- ...
-
- Kernel command line: mtdparts=physmap-flash.0:512k(bootloader),512k(env),4M(kernel),-(root);
- mxc_nand:1M(bootloader),1M(env),4M(kernel),-(root)
-
Creating root= options for the Kernel
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -380,3 +355,33 @@ If the preconfigured paths or names are not suitable, they can be adjusted in
``boot net`` will then retrieve the kernel (and also the device tree and
initramfs, if used) over TFTP and boot it.
+
+mtdparts/blkdevparts fixup
+--------------------------
+
+All variables starting with ``global.linux.mtdparts.`` or ``global.linux.blkdevparts``
+are concatenated to a ``mtdparts=`` or ``blkdevparts=`` parameter to the
+kernel, respectively.
+This makes it possible to consistently partition devices with the :ref:`command_addpart`
+command and pass the same string as used with addpart to the Kernel:
+
+.. code-block:: sh
+
+ norparts="512k(bootloader),512k(env),4M(kernel),-(root)"
+ nandparts="1M(bootloader),1M(env),4M(kernel),-(root)"
+
+ global linux.mtdparts.nor0="physmap-flash.0:$norparts"
+ global linux.mtdparts.nand0="mxc_nand:$nandparts"
+
+ addpart /dev/nor0 $norparts
+ addpart /dev/nand0 $nandparts
+
+ ...
+
+ bootm zImage
+
+ ...
+
+ Kernel command line: mtdparts=physmap-flash.0:512k(bootloader),512k(env),4M(kernel),-(root);
+ mxc_nand:1M(bootloader),1M(env),4M(kernel),-(root)
+
--
2.47.3
next prev parent reply other threads:[~2026-05-05 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 9:50 [PATCH 0/3] bootm: append automatic parameters after all other linux.bootargs Ahmad Fatoum
2026-05-05 9:50 ` [PATCH 1/3] common: fix help text reference to internal imagicvars Ahmad Fatoum
2026-05-05 9:50 ` Ahmad Fatoum [this message]
2026-05-05 9:51 ` [PATCH 3/3] bootm: append automatic parameters after all other linux.bootargs Ahmad Fatoum
2026-05-05 12:45 ` Alexander Shiyan
2026-05-07 11:17 ` (subset) " Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260505095137.1123867-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox