From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH v3] genericarm64 core-image-initramfs-boot: remove some kernel drivers
Date: Thu, 16 Apr 2026 17:07:33 +0300 [thread overview]
Message-ID: <aeDtJYWC5gku-hd3@nuoska> (raw)
In-Reply-To: <cc1cc03b1118d75b010727706abacbb4c4f7f345.camel@linuxfoundation.org>
Hi,
On Thu, Apr 16, 2026 at 02:48:13PM +0100, Richard Purdie wrote:
> On Thu, 2026-04-16 at 16:26 +0300, Mikko Rapeli via lists.yoctoproject.org wrote:
> > On Mon, Apr 13, 2026 at 10:27:15AM +0300, Mikko Rapeli via lists.yoctoproject.org wrote:
> > > genericarm64 supports a lot of HW and thus large collection of kernel
> > > drivers are enabled and installed to images by default.
> > > Subset of the kernel drivers are needed in initramfs to mount rootfs
> > > from local mass storage devices. This increases initramfs size a lot
> > > and with new kernel config updates even more. Thus remove kernel
> > > drivers from initramfs image which are not needed for mounting
> > > rootfs from local mass storage devices. GPU, Bluetooth, NFC,
> > > sound, networking etc support is not needed in the initramfs.
> > >
> > > According to buildhistory core-image-initramfs-boot size is reduced
> > > from 118 to 83 Mb.
> >
> > In my oe-core master branch builds core-image-initramfs-boot is now failing
> > due to size limits:
> >
> > https://gitlab.com/Linaro/trustedsubstrate/gpit/-/jobs/13951723488
> >
> > 2026-04-16 13:04:26 - ERROR��� - ERROR: core-image-initramfs-boot-1.0-r0 do_image_cpio: The initramfs size 282121(K) exceeds INITRAMFS_MAXSIZE: 280000(K)
> > 2026-04-16 13:04:26 - ERROR��� - ERROR: core-image-initramfs-boot-1.0-r0 do_image_cpio: You can set INITRAMFS_MAXSIZE a larger value. Usually, it should
> > 2026-04-16 13:04:26 - ERROR��� - ERROR: core-image-initramfs-boot-1.0-r0 do_image_cpio: be less than 1/2 of ram size, or you may fail to boot it.
> >
> > This patch could be one fix.
> >
> > But is this visible in auto-builder side builds? Or have the genericarm64
> > poky-altcfg distro builds been disabled?
>
> We're not seeing it there, the builds should be running though.
Ok. Maybe it's the linux-firmware update which just tipped genericarm64
core-image-initramfs-boot over the size limit.
I hope this patch would be fine as a fix.
Cheers,
-Mikko
next prev parent reply other threads:[~2026-04-16 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18A5D9F18A3D8C50.777565@lists.yoctoproject.org>
2026-04-16 13:26 ` [poky] [PATCH v3] genericarm64 core-image-initramfs-boot: remove some kernel drivers Mikko Rapeli
2026-04-16 13:48 ` Richard Purdie
2026-04-16 14:07 ` Mikko Rapeli [this message]
2026-04-13 7:27 Mikko Rapeli
2026-04-17 9:10 ` [poky] " Richard Purdie
2026-04-17 9:25 ` Mikko Rapeli
2026-04-17 12:06 ` Richard Purdie
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=aeDtJYWC5gku-hd3@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=poky@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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