From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: Re: [RFC] initramfs support for linux-handhelds-2.6
Date: Mon, 25 Feb 2008 10:15:11 +0100 [thread overview]
Message-ID: <fpu0uv$oi8$1@ger.gmane.org> (raw)
In-Reply-To: <20080225014825.36e60782@widy.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Sokolovsky schreef:
| Hello,
|
| Failing to add generic and fully automated kernel-with-initramfs build,
| I have patch to add external initramfs to kernel for linux-hh. I'd
| still like to establish conventions for other kernel recipes to follow,
| so here're the patch for suggestion. The idea is simple:
|
| 1. KERNEL_INITRAMFS_PATH is set to the full path of cpio.gz image to
| use as initramfs. Empty value (default) means don't use initramfs. If
| file doesn't exist, build fails with an error message (content is left
| to specific recipe - there unfortunately doesn't seem to be a way to
| sensibly provide detailed one in generic case).
|
| 2. KERNEL_INITRAMFS_PATH is considered a distro realm, like for example
| kernel PREFERRED_VERSION. Below, angstrom distro config sets it.
| +KERNEL_INITRAMFS_PATH =
"${TMPDIR}/deploy/uclibc/images/${MACHINE}/initramfs-bootmenu-image-${MACHINE}.cpio.gz"
| + if [ -n "${KERNEL_INITRAMFS_PATH}" -a "${ANGSTROM_MODE}" == "glibc"
]; then
A number of things:
1) Make the initramfs generation a seperate function (or task) that can
be called at will, instead of always being called in do_compile_prepend
2) Keep it simple and keep the kernel and initramfs in the same libc
realm, so a uclibc based initramfs needs a uclibc kernel (I known there
is no such thing, but you get the idea). That way you can just fish it
out of DEPLOY_DIR_IMAGE
3) Add an initramfs-<kernel-name_version>.bb that does
~ require <kernel-name_version>.bb
~ FILESPATH = "/path/magic/whatever"
~ do_compile_prepend() { do_initramfs}
This involves some extra build time ('uclibc' kernel build and a
'uclibc' initramfs kernel build), but is more transparent and less error
prone than your plan. I think it even avoids the dependency problems :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHwocfMkyGM64RGpERAg7gAJ0W2JIsJNjLiJoGwAVHdYvmNa8jPACfVc0x
0UDx1orbRuEtQB5eITl23N0=
=8LWE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-25 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 23:48 [RFC] initramfs support for linux-handhelds-2.6 Paul Sokolovsky
2008-02-25 9:15 ` Koen Kooi [this message]
2008-02-25 10:22 ` Paul Sokolovsky
[not found] ` <fpuebs$5oa$1@ger.gmane.org>
2008-02-25 13:57 ` [Angstrom-devel] " Paul Sokolovsky
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='fpu0uv$oi8$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.