From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Cleiton Bueno <cleiton.bueno@b2open.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] Simple solution to create a non-root partition image?
Date: Mon, 4 May 2026 15:55:30 +0200 [thread overview]
Message-ID: <ee871781-e439-45f2-9567-dbb8c9374075@rootcommit.com> (raw)
In-Reply-To: <CAA-i2Lw6FS=b6UkJjq42RHR-aHtvqqeULxL0e3UxMNuVhZCx2g@mail.gmail.com>
Hi Cleiton
On 5/4/26 3:39 PM, Cleiton Bueno wrote:
> Wouldn't enabling the TEZI_DATA_ENABLED variable and using this extra
> partition work?
>
> https://git.toradex.com/meta-toradex-bsp-common.git/tree/classes/image_type_tezi.bbclass?h=scarthgap-7.x.y#n37
>
> I already needed to create a class for a client with 2 additional
> partitions and I made a copy of image_type_tezi.bbclass and customized
> it for my client.
>
> And create an .ext4 file and put it in this partition?
Absolutely! That's exactly what I intend to do.
I've also tweaked image_type_tezi.bbclass to fit my project needs (a
boot partition, two rootfilesystems and two extra partitions).
Thanks for contributing to this discussion!
Cheers
Michael.
--
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
next prev parent reply other threads:[~2026-05-04 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 20:40 Simple solution to create a non-root partition image? Michael Opdenacker
2026-05-04 8:47 ` [yocto] " Quentin Schulz
2026-05-04 13:08 ` Michael Opdenacker
2026-05-04 13:15 ` Quentin Schulz
2026-05-04 13:39 ` Cleiton Bueno
2026-05-04 13:55 ` Michael Opdenacker [this message]
2026-05-14 16:45 ` Michael Opdenacker
[not found] ` <684BE1E8-500C-4169-B5AF-C72E064F28E8@siliconbladeconsultants.com>
2026-05-04 13:27 ` Michael Opdenacker
2026-05-04 14:05 ` Francesco Cervigni
2026-05-14 16:27 ` Michael Opdenacker
2026-05-04 17:58 ` Francesco Valla
2026-05-06 9:44 ` Felix Mellmann
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=ee871781-e439-45f2-9567-dbb8c9374075@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=cleiton.bueno@b2open.com \
--cc=yocto@lists.yoctoproject.org \
/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