linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: "tiejun.chen" <tiejun.chen@windriver.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, uboot <u-boot@lists.denx.de>
Subject: Re: cuImage and multi image?
Date: Mon, 20 Sep 2010 10:52:30 -0700	[thread overview]
Message-ID: <AANLkTikrYdi=V6jM4HS3V4XzMutGdkPA2qHRBgviKHM8@mail.gmail.com> (raw)
In-Reply-To: <4C91C77B.8080501@windriver.com>

>> I have a cuImage kernel in order to support legacy u-boot and a
>> ramdisk image. Kernel boots fine if these two images are separate and
>> "bootm $kernel $ramdisk" is used. But I can not make it to work using
>> a single multi image that contains the kernel and ramdisk images. Is
>> it even technically possible to boot a multi-image with cuboot
>> wrapper?
>
> Try the following steps:
> ------
> 1. cp <your ramdisk.gz> arch/powerpc/boot/ramdisk.image.gz
> 2. make cuImage.initrd.<your target>
>
> You can get one Image, cuImage.initrd.<your target>, including kernel and ramdisk.

A follow up question. With this method, the total image size
(uncompressed) is limited to the 4MB (the link address of the boot
wrapper)?

Thanks,
-Shawn.

  parent reply	other threads:[~2010-09-20 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16  6:21 cuImage and multi image? Shawn Jin
2010-09-16  7:30 ` tiejun.chen
2010-09-16  7:49   ` Shawn Jin
2010-09-20 17:52   ` Shawn Jin [this message]
2010-09-21  1:03     ` Chen, Tiejun
2010-09-21 17:52       ` [U-Boot] " Scott Wood
2010-09-21 23:45         ` Chen, Tiejun
2010-09-22  5:43           ` Shawn Jin
2010-09-22 14:28             ` Chen, Tiejun
2010-09-22 20:22               ` Shawn Jin
2010-09-23  6:30                 ` Shawn Jin
2010-09-23 13:33                 ` Chen, Tiejun

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='AANLkTikrYdi=V6jM4HS3V4XzMutGdkPA2qHRBgviKHM8@mail.gmail.com' \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tiejun.chen@windriver.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).