All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building a rootfs, without building a kernel
Date: Thu, 03 Jul 2008 13:20:00 -0400	[thread overview]
Message-ID: <486D0A40.9050608@balister.org> (raw)
In-Reply-To: <1CADFA951940554D86FBD8B24BBFF3A0018FA35F@LONMLVEM08.e2k.ad.ge.com>

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

Welch, Martyn (GE EntSol, Intelligent Platforms) wrote:
> Ben Lau wrote:
>>> Possibly, we should create a dummy kernel bb file since this may be
>>> the best solution for the general case of people building images
>>> without a working kernel bb file. 
>>>
>>> Philip
>>>
>> I am not quite understand why OpenEmbedded force to generate kernel
>> and the dependence would force it to be installed in the user land. As
>> the kernel is usually installed on another partition. It should not be
>> a part of the file system image.
>>
> 
> But any drivers, etc. built as modules would need to be included in the
> system's image and that at least would be a dependence.

Agreed. The image recipes have most modules included as RECOMMENDS so 
the image builds even if the module is not present. The technique I am 
using is for cases when you need a rootfs, before you have a working 
kernel recipe. You can copy the modules onto the rootfs if needed.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2008-07-03 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 20:04 Building a rootfs, without building a kernel Philip Balister
2008-06-24 20:16 ` Koen Kooi
2008-06-24 21:01   ` Philip Balister
2008-06-26 12:03 ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-06-29 22:29 ` Michael 'Mickey' Lauer
2008-06-29 23:08 ` David Baird
2008-07-01 18:14   ` Philip Balister
2008-07-02  7:36     ` Ben Lau
2008-07-03 15:03       ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-07-03 17:20         ` Philip Balister [this message]
2008-07-04 13:59           ` Rodrigo Vivi

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=486D0A40.9050608@balister.org \
    --to=philip@balister.org \
    --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.