From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"Suzuki K. Poulose" <suzuki@in.ibm.com>,
"horms@verge.net.au" <horms@verge.net.au>,
"mat@brain-dump.org" <mat@brain-dump.org>
Subject: Re: [PATCH 3/3] ppc/uImage: Add support for RAM Disks
Date: Wed, 16 Jan 2013 18:30:34 +0100 [thread overview]
Message-ID: <20130116173034.GC20369@linutronix.de> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A83353D@039-SN1MPN1-001.039d.mgd.msft.net>
* McClintock Matthew-B29882 | 2013-01-14 15:14:16 [+0000]:
>On Sun, Jan 13, 2013 at 11:14 PM, Suzuki K. Poulose <suzuki@in.ibm.com> wrote:
>> On 01/11/2013 12:41 PM, McClintock Matthew-B29882 wrote:
>>>
>>> On Fri, Jan 11, 2013 at 12:42 AM, Suzuki K. Poulose <suzuki@in.ibm.com>
>>> wrote:
>>>>
>>>> From: Suzuki K. Poulose <suzuki@in.ibm.com>
>>>>
>>>> Handle the RAM Disks in uImage format
>>>
>>>
>>> As opposed to simple ext2.gz ramdisk?
>
>OK - it's been a while but we only supported uImage for kernel image
>not ramdisk. That's what threw me off when I wrote this email I
>believe.
Who is "we"? Did you use kexec and pass ext2.gz as a ramdisk?
u-boot supports this like for ever. You start the kernel via
bootm x y z
where y is the address of the ramdisk / initrd. passing the address the
ext2.gz files does not work.
As an alternative to this you can only pass x to bootm and the image has
the "uImage.FIT" format which can contain the kernel, device tree and a
ramdisk in one piece.
>-M
Sebastian
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-01-16 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 6:41 [PATCH 0/3] kexec: Support for uImage RAMDisks Suzuki K. Poulose
2013-01-11 6:41 ` [PATCH 1/3] kexec/uImage: Return the image type for uImage_probe Suzuki K. Poulose
2013-01-16 17:20 ` Sebastian Andrzej Siewior
2013-01-17 3:10 ` Suzuki K. Poulose
2013-01-11 6:41 ` [PATCH 2/3] kexec/uImage: Recognize uImage RAM Disks Suzuki K. Poulose
2013-01-11 6:42 ` [PATCH 3/3] ppc/uImage: Add support for " Suzuki K. Poulose
2013-01-11 7:11 ` McClintock Matthew-B29882
2013-01-14 5:14 ` Suzuki K. Poulose
2013-01-14 15:14 ` McClintock Matthew-B29882
2013-01-16 17:30 ` Sebastian Andrzej Siewior [this message]
2013-01-16 17:37 ` McClintock Matthew-B29882
2013-01-16 17:26 ` Sebastian Andrzej Siewior
2013-01-17 9:47 ` Suzuki K. Poulose
2013-01-27 16:39 ` Sebastian Andrzej Siewior
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=20130116173034.GC20369@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=B29882@freescale.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=lethal@linux-sh.org \
--cc=mat@brain-dump.org \
--cc=suzuki@in.ibm.com \
/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