From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Are deferred Initcalls possible with a Linux 2.6.39 Kernel?
Date: Fri, 7 Mar 2014 16:21:06 +0100 [thread overview]
Message-ID: <20140307152105.GC2917@piout.net> (raw)
In-Reply-To: <5319D2C8020000460004B7A4@gwia2.rz.hs-offenburg.de>
On 07/03/2014 at 14:08:08 +0100, Frank Ihle wrote :
> Hi everyone,
>
> I want to load several modules not at boot time, but afterwards when system is ready to operate. There are the deferred initcalls, that do exactly what I want as explained on http://elinux.org/Deferred_Initcalls.
>
deferred_initcall is not for modules but for driver statically compiled
in the kernel. Is that what you are looking for ?
> Now to use them I need to apply a patch. On the given page, there are patches for Linux 2.6.26, 2.6.27, 2.6.28 and 3.10, unfortunately I'm using a Linux 2.6.39 and non of those patches can be applied successfully (Patch fails and If I make an Image afterwards, the "/proc/deferred_initcall" is not included)
>
> Does anyone know if there are further patches or is there a workaround for Linux 2.6.39?
>
I would say that the patch is sufficiently small to be ported easily on
any kernel version.
My guess would be that the 3.10 one is the one you should start with.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-07 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:08 [Buildroot] Are deferred Initcalls possible with a Linux 2.6.39 Kernel? Frank Ihle
2014-03-07 15:21 ` Alexandre Belloni [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=20140307152105.GC2917@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=buildroot@busybox.net \
/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