From: Denys Dmytriyenko <denys@ti.com>
To: Bernard Mentink <bmentink@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Kernel load issue
Date: Mon, 4 Nov 2013 17:16:14 -0500 [thread overview]
Message-ID: <20131104221613.GZ24696@edge> (raw)
In-Reply-To: <CALEed8YYeF-rT6PYb_Js+Ex=QZxHh=FJbuOYUgDTkuCDAmz-vw@mail.gmail.com>
On Tue, Nov 05, 2013 at 10:44:09AM +1300, Bernard Mentink wrote:
> Hi Guys,
>
> I am having trouble loading some kernel CAN modules so that they go in my
> image.
>
> I have the following lines in my layers .conf file:
>
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-can-dev"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-c_can"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-c_can_platform"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-can"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-can-raw"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-mcp2515"
>
> all the modules end up in the rootfs except c_can and c_can_platform.
Because package names cannot have underscores, they are replaced with dashes.
So, corresponding packages to be installed in rootfs are kernel-module-c-can
and kernel-module-c-can-platform.
> All modules are built as modules.
>
> They end up in the deploy/images/modules* tarball, but not in the rootfs ..
>
> Hopefully someone can suggest a solution.
>
> Cheers,
> Bernie
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
prev parent reply other threads:[~2013-11-04 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 21:44 Kernel load issue Bernard Mentink
2013-11-04 22:16 ` Denys Dmytriyenko [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=20131104221613.GZ24696@edge \
--to=denys@ti.com \
--cc=bmentink@gmail.com \
--cc=meta-ti@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.