public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com, jan.kiszka@siemens.com
Cc: henning.schild@siemens.com
Subject: Re: [PATCH v3 1/1] Add support to build binary version of DKMS kernel modules
Date: Wed, 28 Apr 2021 14:03:53 +0300	[thread overview]
Message-ID: <20bd033c-02cc-5a4c-727e-94865fc28df3@ilbers.de> (raw)
In-Reply-To: <20210426161602.13875-2-felix.moessbauer@siemens.com>

26.04.2021 19:16, Felix Moessbauer wrote:
> This patch adds support to build and install a kernel module that is available
> via a debian DKMS package.
> As it is hard to directly build and install the package we create and distribute
> a meta package that is independent of the kernel version.
> In that package, we depend on the versioned prebuild kernel module package.
>
> To build the dkms module, we add two tasks and directly
> use dkms to build the debian package containing the binary module
> Then we just copy the binary-module debian package to the workdir,
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>

There is an issue on building example-dkms-module-686-pae for 
mc:qemui386-stretch:isar-image-base target in case of ISAR_CROSS_COMPILE 
is set to 0:
 >Gathering binaries...Error! No modules built for 4.9.0-15-686-pae (i386).
Please try and fix.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov


  reply	other threads:[~2021-04-28 11:04 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     ` [PATCH v3 0/1] " Felix Moessbauer
2021-04-26 16:16     ` [PATCH v3 1/1] " Felix Moessbauer
2021-04-28 11:03       ` Anton Mikanovich [this message]
2021-04-30 14:02 [PATCH v3 0/1] " Felix Moessbauer
2021-04-30 14:02 ` [PATCH v3 1/1] " Felix Moessbauer
2021-04-30 17:19   ` Henning Schild

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=20bd033c-02cc-5a4c-727e-94865fc28df3@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=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