From: Ryan Eatmon <reatmon@ti.com>
To: <openembedded-core@lists.openembedded.org>
Subject: image.bbclass question
Date: Wed, 2 Aug 2023 11:41:01 -0500 [thread overview]
Message-ID: <c447aa42-9eae-ce9c-356f-ae3133c00418@ti.com> (raw)
I am trying to add support for the INITRAMFS_MAXSIZE into the meta-ti
layer for our tiny image.
I have added the following to our tiny image file:
INITRAMFS_FSTYPES += "cpio cpio.xz"
INITRAMFS_MAXSIZE = "65536"
But I'm not seeing any errors about the image being too big being printed.
In looking at the code in question:
# Check the initramfs size against INITRAMFS_MAXSIZE (if set)
if image_fstypes == initramfs_fstypes != '' and initramfs_maxsize:
initramfs_maxsize_int = int(initramfs_maxsize)
if base_size > initramfs_maxsize_int:
bb.error("The initramfs size %d(K) exceeds
INITRAMFS_MAXSIZE: %d(K)" % \
(base_size, initramfs_maxsize_int))
bb.error("You can set INITRAMFS_MAXSIZE a larger value.
Usually, it should")
bb.fatal("be less than 1/2 of ram size, or you may fail to
boot it.\n")
What is the purpose of the:
if image_fstypes == initramfs_fstypes != ''
It seems to looking for the ONLY images being built are the exact same
as the INITRAMFS_FSTYPES... Shouldn't that be more of an intersection
check? If any of the INITRAMFS_FSTYPES are in the IMAGE_FSTYPES, then
check the size?
Or am I missing something?
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
next reply other threads:[~2023-08-02 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 16:41 Ryan Eatmon [this message]
2023-08-02 17:17 ` [OE-core] image.bbclass question Christopher Larson
2023-08-02 18:14 ` Ryan Eatmon
[not found] ` <1777A39C626FDD4B.20033@lists.openembedded.org>
2023-08-02 18:23 ` Ryan Eatmon
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=c447aa42-9eae-ce9c-356f-ae3133c00418@ti.com \
--to=reatmon@ti.com \
--cc=openembedded-core@lists.openembedded.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