From: Mike Looijmans <mike.looijmans@topic.nl>
To: <yocto@yoctoproject.org>
Subject: Re: External Linux Kernel Module
Date: Thu, 11 Dec 2014 07:59:22 +0100 [thread overview]
Message-ID: <548940CA.7040902@topic.nl> (raw)
In-Reply-To: <7B6FE55CD594D7478CED8A39DF3BFC0A5E6FA1D4@UT40SVCWEM001.atk.com>
On 12/10/2014 06:42 AM, Moore, Thomas (FtWorth) wrote:
> Hello,
>
> I’m working on incorporating an external kernel module based on the hello-mod
> skeleton recipe. Everything was going well until I added the following line to
> my machine configuration:
>
> MACHINE_EXTRA_RDEPENDS += "kernel-module-hello”
>
> Attempting to run “bitbake core-image-base” then leads to the following error:
>
> no package provides kernel-module-hello
>
> After digging through the .bbclass files in the meta folder, I’m beginning to
> think that the following comment in the hello-mod_0.1.bb file is no longer true:
>
> # The inherit of module.bbclass will automatically name module packages with
>
> # "kernel-module-" prefix as required by the oe-core build environment.
>
> Adding the following lines to the end of hello-mod_0.1.bb allows the image to
> be successfully created:
>
> PROVIDES = "kernel-module-hello"
>
> RPROVIDES_${PN} = "kernel-module-hello"
>
> Has something been changed in module.bbclass? Is it even required to have to
> have the “kernel-module-“ prefix?
I think that comment is outdated or something that someone wanted to implement
some day or so.
I've always just named my kernel module recipes "kernel-module-XXX.bb".
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
prev parent reply other threads:[~2014-12-11 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 5:42 External Linux Kernel Module Moore, Thomas (FtWorth)
2014-12-11 6:59 ` Mike Looijmans [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=548940CA.7040902@topic.nl \
--to=mike.looijmans@topic.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox