From: "Christos Gavros" <gavrosc@yahoo.com>
To: docs@lists.yoctoproject.org
Subject: Re: [PATCH] ref-manual/variables.rst: document the INITRAMFS_MAXSIZE variable
Date: Wed, 23 Apr 2025 12:24:44 -0700 [thread overview]
Message-ID: <28281.1745436284133202831@lists.yoctoproject.org> (raw)
In-Reply-To: <5436.1743603561759061812@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
hi Antonin and Quentin
i had a further look on that.
When initramfs is included in build (INITRAMFS_IMAGE = "core-image-minimal-initramfs" in local.conf)
then the 'IMAGE_ROOTFS' is pointing to build/tmp/work/qemux86_64-poky-linux/core-image-minimal-initramfs/1.0/rootfs.
This directory is approximately 115000kb.
If INITRAMFS_MAXSIZE = "1100000" then the error is generated.
If INITRAMFS_MAXSIZE = "1600000" then the build is ok.
So i think that the INITRAMFS_MAXSIZE refers to the size of the directory and not the final image type.
The condition " if image_fstypes == initramfs_fstypes != '' and initramfs_maxsize: ", exists
because in the recipe "core-image-minimal-initramfs" there is the assignment IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}".
So the INITRAMFS_MAXSIZE is evaluated only when one of the initramfs recipes is included.
Shall i submit a v2 ?
Br
Christos
[-- Attachment #2: Type: text/html, Size: 1083 bytes --]
next prev parent reply other threads:[~2025-04-23 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250328205213.93625-1-gavrosc.ref@yahoo.com>
2025-03-28 20:52 ` [PATCH] ref-manual/variables.rst: document the INITRAMFS_MAXSIZE variable Christos Gavros
2025-03-31 8:51 ` [docs] " Quentin Schulz
2025-03-31 9:24 ` Christos Gavros
2025-04-01 19:43 ` Christos Gavros
2025-04-02 9:15 ` [docs] " Quentin Schulz
2025-04-02 12:24 ` Antonin Godard
2025-04-02 14:19 ` Christos Gavros
2025-04-23 19:24 ` Christos Gavros [this message]
2025-04-24 8:04 ` [docs] " Antonin Godard
2025-04-24 15:18 ` Christos Gavros
2025-04-25 7:34 ` [docs] " Antonin Godard
2025-04-25 8:35 ` Christos Gavros
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=28281.1745436284133202831@lists.yoctoproject.org \
--to=gavrosc@yahoo.com \
--cc=docs@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