From: "Denys Dmytriyenko" <denis@denix.org>
To: scott.branden@broadcom.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] unwanted linux kernel image added to /boot directory
Date: Mon, 15 Mar 2021 19:57:32 -0400 [thread overview]
Message-ID: <20210315235732.GS4892@denix.org> (raw)
In-Reply-To: <a8c3bbca-1b5c-5353-9a0a-c7ecebc2fc32@broadcom.com>
On Mon, Mar 15, 2021 at 04:39:56PM -0700, Scott Branden via lists.openembedded.org wrote:
> Hello,
>
> There seems to be a problem when a kernel module is added to an initramfs
> image.
>
> As soon as I add a recipe which installs an external kernel module into an
> initramfs image it automatically installs the linux kernel image in a /boot
> directory.
>
> This is really bad as it increases the size of the initramfs image.
>
> /boot/Image should not be installed in the image when an external kernel
> module is added to an image.
>
> Can someone suggest a fix to this issue?
There is an ages-old control knob for that, read here:
https://git.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n623
In your machine or distro config, you can set this as:
RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""
But that will affect all your images for a given machine. If you need to only
do it selectively for your initramfs image, but keep the standard behavior for
other images, you can do something like this in corresponding recipe:
ROOTFS_POSTPROCESS_COMMAND += "empty_boot_dir; "
empty_boot_dir () {
rm -rf ${IMAGE_ROOTFS}/boot/*
}
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2021-03-15 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 23:39 unwanted linux kernel image added to /boot directory Scott Branden
2021-03-15 23:49 ` [OE-core] " Khem Raj
2021-03-16 0:12 ` Denys Dmytriyenko
2021-03-15 23:57 ` Denys Dmytriyenko [this message]
[not found] ` <45e3e633-c15b-9010-a085-e34f6d7d0d1e@broadcom.com>
[not found] ` <20210316183628.GH18041@denix.org>
2021-03-16 18:38 ` Denys Dmytriyenko
[not found] <166CA878538D6557.30053@lists.openembedded.org>
2021-03-16 3:13 ` Scott Branden
2021-03-16 10:47 ` Max Krummenacher
2021-03-16 16:55 ` Khem Raj
2021-03-16 17:39 ` Denys Dmytriyenko
2021-03-16 18:24 ` Denys Dmytriyenko
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=20210315235732.GS4892@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.branden@broadcom.com \
/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