From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] where in the docs does it explain wic directives "part SPL"?
Date: Fri, 18 Sep 2026 09:21:19 +0200 [thread overview]
Message-ID: <DLI9EGQ6G3YP.1WQSA9VK3RGIE@bootlin.com> (raw)
In-Reply-To: <16fc349e-53a1-715f-0876-75acc3a41988@crashcourse.ca>
Hi,
On Thu Sep 17, 2026 at 10:18 PM CEST, Robert P. J. Day wrote:
>
> i'm trying to cross-reference all the wic explanations, and i read
> in the reference:
>
> https://docs.yoctoproject.org/ref-manual/kickstart.html#openembedded-kickstart-wks-reference
>
> this in section 10.2:
>
> part [mntpoint]
> partition [mntpoint]
>
> If you do not provide mntpoint, Wic creates a partition but does not
> mount it.
>
> The mntpoint is where the partition is mounted and must be in one of
> the following forms:
>
> /path: For example, “/”, “/usr”, or “/home”
>
> swap: The created partition is used as swap space
>
> fair enough, but nothing there covers lines like this that you find
> for i.MX targets:
>
> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk
> --no-table --align 1
> part u-boot --source rawcopy
> --sourceparams="file=${UBOOT_BINARY}.tagged" --ondisk mmcblk
> --no-table --align 69
>
>
> where is the explanation of examples like "part SPL" and "part
> u-boot"?
We are missing documentation on the various plugins supported by Wic. I would
like to get around to them at some point, but patches welcome of course.
Note: "SPL" and "u-boot" are just names here, the part that is missing doc is
"rawcopy".
Antonin
prev parent reply other threads:[~2026-09-18 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 20:18 where in the docs does it explain wic directives "part SPL"? Robert P. J. Day
2026-09-18 7:21 ` Antonin Godard [this message]
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=DLI9EGQ6G3YP.1WQSA9VK3RGIE@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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