* How to include kernel module without including the kernel in the rootfs?
@ 2014-04-10 15:32 Patrick Doyle
2014-04-10 15:35 ` Bruce Ashfield
0 siblings, 1 reply; 3+ messages in thread
From: Patrick Doyle @ 2014-04-10 15:32 UTC (permalink / raw)
To: yocto@yoctoproject.org
I just added a custom kernel module to my build, and now my rootfs
includes a copy of my kernel (thus making it too large to fit in my
pinhole sized root partition).
Is there any way to prevent the kernel from being included in the
rootfs? Do modutils require a kernel image in order to function
properly?
My recipe contains
inherit module
So I'm expecting that the module class does magic that results in the
kernel getting installed.
Is there a flag I can set to say "Don't do that?".
Thanks.
--wpd
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to include kernel module without including the kernel in the rootfs?
2014-04-10 15:32 How to include kernel module without including the kernel in the rootfs? Patrick Doyle
@ 2014-04-10 15:35 ` Bruce Ashfield
2014-04-10 18:05 ` Patrick Doyle
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Ashfield @ 2014-04-10 15:35 UTC (permalink / raw)
To: Patrick Doyle, yocto@yoctoproject.org
On 14-04-10 11:32 AM, Patrick Doyle wrote:
> I just added a custom kernel module to my build, and now my rootfs
> includes a copy of my kernel (thus making it too large to fit in my
> pinhole sized root partition).
>
> Is there any way to prevent the kernel from being included in the
> rootfs? Do modutils require a kernel image in order to function
> properly?
Clear this in your kernel recipe:
# Allow machines to override this dependency if kernel image files are
# not wanted in images as standard
RDEPENDS_kernel-base ?= "kernel-image"
and you'll get no kernel image, and yes, modules will work.
Bruce
>
> My recipe contains
>
> inherit module
>
> So I'm expecting that the module class does magic that results in the
> kernel getting installed.
>
> Is there a flag I can set to say "Don't do that?".
>
> Thanks.
>
> --wpd
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to include kernel module without including the kernel in the rootfs?
2014-04-10 15:35 ` Bruce Ashfield
@ 2014-04-10 18:05 ` Patrick Doyle
0 siblings, 0 replies; 3+ messages in thread
From: Patrick Doyle @ 2014-04-10 18:05 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto@yoctoproject.org
Hi Bruce,
Thank you very much. That did the trick.
--wpd
On Thu, Apr 10, 2014 at 11:35 AM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 14-04-10 11:32 AM, Patrick Doyle wrote:
>>
>> I just added a custom kernel module to my build, and now my rootfs
>> includes a copy of my kernel (thus making it too large to fit in my
>> pinhole sized root partition).
>>
>> Is there any way to prevent the kernel from being included in the
>> rootfs? Do modutils require a kernel image in order to function
>> properly?
>
>
> Clear this in your kernel recipe:
>
> # Allow machines to override this dependency if kernel image files are
> # not wanted in images as standard
> RDEPENDS_kernel-base ?= "kernel-image"
>
> and you'll get no kernel image, and yes, modules will work.
>
> Bruce
>
>
>>
>> My recipe contains
>>
>> inherit module
>>
>> So I'm expecting that the module class does magic that results in the
>> kernel getting installed.
>>
>> Is there a flag I can set to say "Don't do that?".
>>
>> Thanks.
>>
>> --wpd
>>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-04-10 18:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-10 15:32 How to include kernel module without including the kernel in the rootfs? Patrick Doyle
2014-04-10 15:35 ` Bruce Ashfield
2014-04-10 18:05 ` Patrick Doyle
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.