From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: SH7751R - STRANGE initramfs/rootfs behavior
Date: Tue, 08 Apr 2008 02:06:20 +0000 [thread overview]
Message-ID: <20080408020620.GA14114@linux-sh.org> (raw)
In-Reply-To: <9e0cf0bf0804070616y72f1bf4er6dcbb23188937543@mail.gmail.com>
On Mon, Apr 07, 2008 at 04:16:01PM +0300, Alon Bar-Lev wrote:
> I am trying to boot 2.6.24 kernel on SH7751R big endian (sh4eb) using
> embedded initramfs, anyone have this configuration working?
>
> I use zImage converted to srec using objcopy, load the srec into
> memory and jump to the load address of the kernel.
>
> The kernel boots, but when trying to decompress the initramfs image it
> fails with "crc error", resulting from lib/inflate.c::gunzip:1250.
>
> Has anyone got this error? The initramfs image is correct. I also
> dumped the memory of __initramfs_start->__initramfs_start and verified
> that it matches the initramfs image on usr/initramfs_data.cpio.gz.
>
I've noticed this on an SH7203 (SH-2A FPU) board, which is also
big-endian. It seems to be an endianness issue, in that it's never show
up on any of the little endian configurations. If your board is
endianness selectable, I'd suggest trying little endian and seeing if
that works.
Little endian certainly gets the bulk of the testing, so it's quite
possible that there are some things broken on big endian.
next prev parent reply other threads:[~2008-04-08 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:16 SH7751R - STRANGE initramfs/rootfs behavior Alon Bar-Lev
2008-04-07 13:19 ` Alon Bar-Lev
2008-04-08 2:06 ` Paul Mundt [this message]
2008-04-08 3:20 ` David McCullough
2008-04-08 3:27 ` Paul Mundt
2008-04-08 5:11 ` Alon Bar-Lev
2008-04-08 5:14 ` Alon Bar-Lev
2008-04-10 16:51 ` Alon Bar-Lev
2008-05-13 8:38 ` Paul Mundt
2008-05-14 19:32 ` Roni Feldman
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=20080408020620.GA14114@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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.