From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v5 0/5] Provide infrastructure and examples for custom kernels and modules
Date: Thu, 15 Feb 2018 16:13:45 +0100 [thread overview]
Message-ID: <8d04dd7a-fd5f-a765-bfbd-319613c77781@siemens.com> (raw)
In-Reply-To: <a98d3cef-a95b-4cc9-9db3-d2861f19caf0@ilbers.de>
On 2018-02-15 16:04, Alexander Smirnov wrote:
>
>
> On 02/15/2018 06:00 PM, Jan Kiszka wrote:
>> On 2018-02-15 15:43, Alexander Smirnov wrote:
>>> On 02/14/2018 12:13 PM, Jan Kiszka wrote:
>>>> This is now finally the promised patches to provide simple patterns for
>>>> building custom kernels for Isar images that replace the distro
>>>> kernels.
>>>> It also provids the same pattern for custom out-of-tree kernel modules.
>>>>
>>>> Changes in v5:
>>>> - dropped merged patches
>>>> - reworked kernel packages naming and selection mechanism to use
>>>> flavor/arch rather them overwriting upstream names
>>>> - fixed rebuilds of the kernel (.version was causing problems)
>>>> - moved kernel build into script - and switched back to include
>>>> pattern
>>>> - provided note on origin of exemplary defconfig
>>>> - add KERNEL_DEFCONFIG variable
>>>>
>>>> Jan
>>>
>>> $ start_vm -a arm -d jessie
>>>
>>> ...
>>>
>>> root@isar:~# modprobe example-module
>>> [ 110.444107] Just an example
>>> modprobe: ERROR: could not insert 'example_module': No anode
>>>
>>>
>>> The same for amd64:
>>>
>>>
>>> root@isar:~# modprobe example-module
>>> [ 38.343926] example_module: loading out-of-tree module taints kernel.
>>> [ 38.353140] Just an example
>>> modprobe: ERROR: could not insert 'example_module': No anode
>>>
>>> Please take a look.
>>>
>>
>> static int __init example_module_init(void)
>> {
>> printk("Just an example\n");
>> return -ENOANO;
>> }
>>
>> module_init(example_module_init);
>>
>> :)
>>
>
> Ouch, didn't notice this. :-(
>
> Do you have any specific reason to have module_init failed? Could we
> have zero return code to test its probe-ability and loading-by-default
> for CI?
I didn't think of CI for this module yet, but that may make more sense
then. Do you plan to write some CI script for that? Then just change the
module code to your needs. It's "just an example". :)
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-15 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 9:13 Jan Kiszka
2018-02-14 9:13 ` [PATCH v5 1/5] Make distro kernel replaceable Jan Kiszka
2018-02-14 9:13 ` [PATCH v5 2/5] Provide include for easy custom kernel builds Jan Kiszka
2018-02-14 19:35 ` [PATCH v6 " Jan Kiszka
2018-02-14 9:13 ` [PATCH v5 3/5] Add custom kernel examples Jan Kiszka
2018-02-14 9:13 ` [PATCH v5 4/5] Provide include file for easy custom module builds Jan Kiszka
2018-02-14 9:13 ` [PATCH v5 5/5] Add exemplary kernel module Jan Kiszka
2018-02-14 15:21 ` [PATCH v6 " Jan Kiszka
2018-02-15 7:15 ` Alexander Smirnov
2018-02-15 7:35 ` [PATCH v6 4/5] Provide include file for easy custom module builds Jan Kiszka
2018-02-15 7:54 ` Alexander Smirnov
2018-02-15 7:54 ` Jan Kiszka
2018-02-15 8:01 ` Alexander Smirnov
2018-02-15 11:24 ` [PATCH v5 0/5] Provide infrastructure and examples for custom kernels and modules Alexander Smirnov
2018-02-15 15:14 ` Jan Kiszka
2018-02-15 14:43 ` Alexander Smirnov
2018-02-15 15:00 ` Jan Kiszka
2018-02-15 15:04 ` Alexander Smirnov
2018-02-15 15:13 ` Jan Kiszka [this message]
2018-02-15 15:27 ` Alexander Smirnov
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=8d04dd7a-fd5f-a765-bfbd-319613c77781@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.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