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: Tue, 01 Jul 2008 14:14:13 -0400	[thread overview]
Message-ID: <486A73F5.2010906@balister.org> (raw)
In-Reply-To: <440abda90806291608g2b4bdfbp71ed039b167e9aa9@mail.gmail.com>

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

David Baird wrote:
> 2008/6/24 Philip Balister <philip@balister.org>:
>> I am trying to build a powerpc root file system for a xilinx ml403 board.
>> Since we do not have a working kernel build for this machine, I tried
>> commenting out the PREFERRED_PROVIDER for virtual/linux. The build then
>> tries to build linux-rt. I tried ASSUME_PROVIDED for the kernel when the
>> preferred provider is not commented out and it still tries to build the
>> kernel.
>>
>> Looking at the dependency graphs seems to suggest the requirement comes from
>> the do_rootfs task.
>>
>> Does anyone know how to build an image, without building a kernel for a
>> machine?
> 
> I have been using this pattern in my BBMASK:
> 
>     BBMASK = "(linux-ml403-slab-2.6.x_git[.].*)"
> 
> and then I made up my own task and image .bb files to establish what
> files I want in my rootfs.  I would also appreciate suggestions on a
> better way to do what to do this.

I pushed changes to linux-ml403-slab (I think I renamed the recipe 
linux-xilinx-slab) so the compile completes. I don't do anything to 
prepare the kernel for actual use. This lets the images build. When I 
finally figure out how to build kernels for Xilinx FPGA based PPC 
boards, I'll worry about creating a bootable kernel. (Unless someone 
beats me to it)

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

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

  reply	other threads:[~2008-07-01 18:17 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 [this message]
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
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=486A73F5.2010906@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.