All of lore.kernel.org
 help / color / mirror / Atom feed
* External Linux Kernel Module
@ 2014-12-10  5:42 Moore, Thomas (FtWorth)
  2014-12-11  6:59 ` Mike Looijmans
  0 siblings, 1 reply; 2+ messages in thread
From: Moore, Thomas (FtWorth) @ 2014-12-10  5:42 UTC (permalink / raw)
  To: yocto@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

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?

Thanks,

Thomas


[-- Attachment #2: Type: text/html, Size: 3630 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: External Linux Kernel Module
  2014-12-10  5:42 External Linux Kernel Module Moore, Thomas (FtWorth)
@ 2014-12-11  6:59 ` Mike Looijmans
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Looijmans @ 2014-12-11  6:59 UTC (permalink / raw)
  To: yocto

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/



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-12-11  6:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-10  5:42 External Linux Kernel Module Moore, Thomas (FtWorth)
2014-12-11  6:59 ` Mike Looijmans

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.