From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: henning.schild@siemens.com, jan.kiszka@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/1] Add support to build binary version of DKMS kernel
Date: Wed, 14 Apr 2021 10:36:16 +0200 [thread overview]
Message-ID: <20210414083617.20940-1-felix.moessbauer@siemens.com> (raw)
DKMS kernel modules provide a way to deliver the sources of a kernel module
along with a machine readable specification of how to build the module
for the currently active kernel. Debian already ships a lot of kernel modules
as DKMS packages.
For embedded images, these DKMS modules are not really an option, as it would
require the image to provide a compiler and build system as well.
For this use-case, DKMS provides a way to pre-build a binary version
of the module for a specific kernel and ship that as a debian package.
Note, that this support is not implemented as part of the debhelpers, but
by DKMS itself.
This series adds support for the described use-case in ISAR.
By that, upstream DKMS modules can be fetched and build for
the image's kernel in ISAR. The generated binary package
can then be installed onto the target image.
To show how to use that, an example is provided in meta-isar.
Best regards,
Felix Moessbauer
Felix Moessbauer (1):
Add support to build binary version of DKMS kernel modules
.../example-dkms-module/igb-uio_20.11.bb | 14 ++++
meta/classes/dkms-module.bbclass | 68 +++++++++++++++++++
2 files changed, 82 insertions(+)
create mode 100644 meta-isar/recipes-kernel/example-dkms-module/igb-uio_20.11.bb
create mode 100644 meta/classes/dkms-module.bbclass
--
2.20.1
next reply other threads:[~2021-04-14 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 8:36 Felix Moessbauer [this message]
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 ` [PATCH v3 0/1] " Felix Moessbauer
2021-04-26 16:16 ` [PATCH v3 1/1] " Felix Moessbauer
2021-04-28 11:03 ` 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=20210414083617.20940-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--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