From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Katu Txakur <katutxakurra@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: using module_autoload
Date: Wed, 29 May 2013 15:55:10 +0100 [thread overview]
Message-ID: <2809625.nUpYsyq62m@helios> (raw)
In-Reply-To: <20130529143948.GM3192@jama>
On Wednesday 29 May 2013 16:39:48 Martin Jansa wrote:
> On Wed, May 29, 2013 at 02:01:11PM +0100, Katu Txakur wrote:
> > Hi,
> > I'm failing to load a kernel module named spike doing this:
> > 1) add the recipe (inherit module), based in a Makefile with
> > modules_install:
> > $(MAKE) INSTALL_MOD_DIR=kernel/drivers/spike -C $(KERNEL_SRC) M=$(SRC)
> > modules_install
> > 2) Add the package to the image with IMAGE_INSTALL += "spike" in the
> > local.conf file
> > 3) In the machine/mymachine.conf I've added
> >
> > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "spike"
> > module_autoload_spike = "spike"
> >
> > The driver gets added to the image and I can load it with insmod spike,
> > however, I would like to load it at boot time.
> > A workaround is to create a file with the name spike.conf and write spike
> > inside. Copying that file to /etc/modules-load.d/spike.conf
> > loads the driver correctly, but I need to do it from a recipe.
> >
> > Can anyone spot what am I doing wrong?
>
> module_autoload won't work with external module unless you inherit also
> kernel-module-split
Note that module.bbclass already does this, so if the external module recipe
already does "inherit module" then that is not the problem.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-29 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 13:01 using module_autoload Katu Txakur
2013-05-29 14:39 ` Martin Jansa
2013-05-29 14:55 ` Paul Eggleton [this message]
2013-05-29 15:32 ` Katu Txakur
2013-05-29 15:34 ` Bruce Ashfield
2013-05-29 15:48 ` Katu Txakur
2013-05-29 16:14 ` Martin Jansa
2013-05-30 8:49 ` Katu Txakur
2013-05-30 11:34 ` Martin Jansa
2013-05-30 16:44 ` Katu Txakur
2013-05-30 17:12 ` Khem Raj
2013-05-30 23:03 ` Katu Txakur
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=2809625.nUpYsyq62m@helios \
--to=paul.eggleton@linux.intel.com \
--cc=katutxakurra@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.