Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Aleksandar Nikolic" <an010@live.com>
To: Mike Looijmans <mike.looijmans@topic.nl>,yocto@lists.yoctoproject.org
Subject: Re: [yocto] Multiple images on the same hardware
Date: Thu, 01 Feb 2024 06:11:55 -0800	[thread overview]
Message-ID: <23652.1706796715918426659@lists.yoctoproject.org> (raw)
In-Reply-To: <1139818a-0492-4feb-9d72-caee7217fea2@topic.nl>

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

> 
> Why don't you just have multiple image recipes?
> 

The initial question was not related to image recipes, but rather to the one linux-kernel recipe. Within the recipe there's no variable I could use to specify which modules get compiled.

> 
> Many images bluntly install "kernel-modules" which throws in everything
> that got built by the kernel recipe. Omit that and you can install kernel
> modules based on exact system requirements.
> 

This is something I will take a look at, thanks for the idea. One "issue" I see with it is that this won't work for built-in modules, however, those "special" scenarios can be covered with modules loaded on demand.

Aleksandar

[-- Attachment #2: Type: text/html, Size: 846 bytes --]

      reply	other threads:[~2024-02-01 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  9:38 Multiple images on the same hardware Aleksandar Nikolic
2024-01-25  9:55 ` [yocto] " Alexander Kanavin
2024-01-25 12:18   ` Aleksandar Nikolic
2024-01-25 14:54     ` Alexander Kanavin
2024-01-25 15:05       ` Aleksandar Nikolic
2024-01-31  7:23       ` Mike Looijmans
2024-01-31 22:07         ` Aleksandar Nikolic
2024-02-01 13:55           ` Mike Looijmans
2024-02-01 14:11             ` Aleksandar Nikolic [this message]

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=23652.1706796715918426659@lists.yoctoproject.org \
    --to=an010@live.com \
    --cc=mike.looijmans@topic.nl \
    --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