From: Hans Beckerus <hans.beckerus@gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: How to make a recipe doing mkimage on a initrd image?
Date: Thu, 21 Feb 2013 20:03:14 +0100 [thread overview]
Message-ID: <51266F72.4040300@gmail.com> (raw)
In-Reply-To: <CABTzgQ54dEyDrbND5Kfy6M4mAGMoyU236V1dOZvW8oLVBWFyzg@mail.gmail.com>
I have created a cpio type rootfs image and are trying to load it as a
initrd ramdisk.
After several boot failures (U-Boot complains it is not a valid image)
I finally realized that the U-Boot version being used on this system
requires that the ramdisk image is also prepended with a mkimage header.
The standard image .bbclass that I am using in my simple recipe does not
seem to have this functionality. Has anyone done a recipe (or image
class?) that is calling mkimage in the do_deploy stage that could help
me on the way here?
I wish to have it work similar to the kernel uImage build for which I
guess the u-boot-native-mkimage is being used.
Hans
prev parent reply other threads:[~2013-02-21 19:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 13:17 Updating uboot to v2013.01 Satya Swaroop Damarla
2013-02-20 16:16 ` Rudolf Streif
2013-02-20 17:01 ` Hans Beckérus
2013-02-20 17:12 ` Satya Swaroop Damarla
2013-02-20 17:46 ` Hans Beckérus
2013-02-20 18:19 ` Satya Swaroop DAMARLA
2013-02-20 18:19 ` Satya Swaroop Damarla
2013-02-21 10:10 ` Satya Swaroop DAMARLA
2013-02-21 16:28 ` Rudolf Streif
2013-02-25 14:58 ` Satya Swaroop DAMARLA
2013-02-25 15:56 ` Satya Swaroop Damarla
2013-02-25 16:02 ` Hans Beckérus
2013-02-26 17:19 ` Rudolf Streif
2013-02-25 16:05 ` Hans Beckérus
2013-02-26 7:36 ` Satya Swaroop Damarla
2013-02-26 17:21 ` Rudolf Streif
2013-02-27 7:44 ` Satya Swaroop Damarla
2013-02-27 15:00 ` Khem Raj
2013-02-28 18:13 ` Rudolf Streif
2013-02-21 19:03 ` Hans Beckerus [this message]
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=51266F72.4040300@gmail.com \
--to=hans.beckerus@gmail.com \
--cc=yocto@yoctoproject.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.