public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com, amikan@ilbers.de, jan.kiszka@siemens.com
Cc: henning.schild@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v3 0/1] Add support to build binary version of DKMS kernel modules
Date: Mon, 26 Apr 2021 18:16:01 +0200	[thread overview]
Message-ID: <20210426161602.13875-1-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <3495ece4-950e-a0ba-64b2-e892f98ec1f8@ilbers.de>

Hi Jan, Anton,

while playing around with various targets, I noticed that the auto-detection of the current
kernel does not work well in the chroot environments.
Instead, we now tell dkms the exact kernel version and architecture based on the debian kernel image
and the target architecture.

Changes since v2:

- do not auto-detect kernel, but extract it from the ISAR arch + kernel image name
- fix builds on ubuntu

Best regards,
Felix

Felix Moessbauer (1):
  Add support to build binary version of DKMS kernel modules

 meta-isar/conf/local.conf.sample              |  5 +-
 .../example-dkms-module.bb                    | 14 ++++
 meta/classes/dkms-module.bbclass              | 75 +++++++++++++++++++
 scripts/ci_build.sh                           |  1 +
 4 files changed, 94 insertions(+), 1 deletion(-)
 create mode 100644 meta-isar/recipes-kernel/example-dkms-module/example-dkms-module.bb
 create mode 100644 meta/classes/dkms-module.bbclass

-- 
2.20.1


  parent reply	other threads:[~2021-04-26 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  8:36 [PATCH 0/1] Add support to build binary version of DKMS kernel Felix Moessbauer
2021-04-14  8:36 ` [PATCH 1/1] Add support to build binary version of DKMS kernel modules Felix Moessbauer
2021-04-14  8:52   ` Henning Schild
2021-04-14  9:03     ` Jan Kiszka
2021-04-15 12:26       ` Henning Schild
2021-04-15 12:41         ` Raphael Lisicki
2021-04-15 12:52         ` Jan Kiszka
2021-04-19 12:45           ` Moessbauer, Felix
2021-04-19 13:33             ` Jan Kiszka
2021-04-22 10:44   ` Anton Mikanovich
2021-04-22 16:02     ` [PATCH v2 0/1] " Felix Moessbauer
2021-04-23  6:03       ` Jan Kiszka
2021-04-22 16:02     ` [PATCH v2 1/1] " Felix Moessbauer
2021-04-26 16:16     ` Felix Moessbauer [this message]
2021-04-26 16:16     ` [PATCH v3 " Felix Moessbauer
2021-04-28 11:03       ` Anton Mikanovich
2021-04-30 14:02 [PATCH v3 0/1] " Felix Moessbauer
2021-04-30 14:47 ` Anton Mikanovich

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=20210426161602.13875-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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