From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Kernel modules
Date: Sun, 17 May 2009 09:16:46 +0100 [thread overview]
Message-ID: <4A0FC7EE.6090903@xora.org.uk> (raw)
In-Reply-To: <fce2a370905170058r407d6b02qa9116bad2d64d292@mail.gmail.com>
Ihar Hrachyshka wrote:
> On Sun, May 17, 2009 at 10:24 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
>
>> On 16-05-09 23:38, Cliff Brake wrote:
>>
>>> On Sat, May 16, 2009 at 5:21 AM, G. Eismann<g.eismann@gmx.net> wrote:
>>>
>>>
>>>> BTW, is there any way to install the modules but not the kernel image?
>>>> I have the kernel in a separate partition, so I don't need it into the
>>>> rootfs.
>>>>
>>> One way is to put the following in the kernel recipe:
>>>
>>> FILES_kernel-image_<machine_name> = ""
>>>
>> Please don't do that, it breaks all sorts of things, one of which is field
>> upgrades.
>>
>
> Your suggestion?
>
>
As nothing depends on kernel-image other than kernel I would suggest
breaking this dependency. Then if you want the image of the kernel on
your rootfs you can explicitly depend on kernel-image in a task.
Graeme
next prev parent reply other threads:[~2009-05-17 8:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 23:22 Kernel modules Chuck Kamas
2009-05-16 7:31 ` Marcin Juszkiewicz
2009-05-16 9:21 ` G. Eismann
2009-05-16 21:38 ` Cliff Brake
2009-05-16 21:50 ` G. Eismann
2009-05-17 7:24 ` Koen Kooi
2009-05-17 7:58 ` Ihar Hrachyshka
2009-05-17 8:16 ` Graeme Gregory [this message]
2009-05-17 18:24 ` Tom Rini
2009-05-16 8:55 ` Koen Kooi
2009-05-16 13:38 ` what not to do in a recipe (was: Kernel modules) Rolf Leggewie
2009-05-16 14:01 ` Ihar Hrachyshka
2009-05-16 14:59 ` what not to do in a recipe Koen Kooi
2009-05-17 18:13 ` Kernel modules Chuck Kamas
2009-05-17 18:26 ` Koen Kooi
2009-05-18 23:23 ` Chuck Kamas
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 13:00 kernel modules Gerd Kautzmann
2023-02-23 22:30 mike mccool
2023-02-24 5:57 ` Jonas Malaco
2011-07-09 16:19 Kernel Modules CACook
2011-07-09 17:12 ` Andreas Philipp
2011-07-09 17:28 ` CACook
2011-07-09 17:39 ` Hugo Mills
2011-07-10 8:24 ` Goffredo Baroncelli
2011-07-09 17:33 ` Helmut Hullen
2011-07-10 6:56 ` Felix Blanke
2011-07-10 7:29 ` Helmut Hullen
2011-07-10 14:24 ` Felix Blanke
2011-07-10 15:57 ` Helmut Hullen
2011-07-10 16:42 ` Felix Blanke
2003-11-14 17:01 kernel Modules Kevin Smith
2003-10-20 14:32 kernel modules David Kesselring
2003-10-20 15:48 ` David Daney
2003-10-20 18:13 ` David Daney
2003-10-20 18:39 ` Ralf Baechle
2003-10-20 21:00 ` Zhang Haitao
2003-10-21 12:34 ` David Kesselring
2001-11-20 20:35 Lee Chin
2001-11-22 2:52 ` Arnaldo Carvalho de Melo
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=4A0FC7EE.6090903@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@lists.openembedded.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.