From: Magnus Damm <damm@opensource.se>
To: linuxppc-embedded@lists.linuxppc.org
Subject: bi_record and initrd
Date: Thu, 14 Nov 2002 16:54:47 +0100 [thread overview]
Message-ID: <3DD3C747.8B7EE5CD@opensource.se> (raw)
Hi all,
The 2.4.19 kernel and the current rsync kernel from
source.mvista.com::linuxppc_2_4 does not work with large initrds.
The bi_record setup code in linux/arch/ppc/boot/simple/misc-embedded.c
doesn't care about the initrd size. So, if you are using a initrd that
crosses a megabyte-boundary you will have your initrd overwritten with
the bi_record. This results in crc error when unpacking the initrd.
The quick fix is to add a offset to the boot-code and to
arch/ppc/kernel/setup.c.
So, what's the long term solution?
Passing a pointer to the kernel?
/ magnus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-11-14 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 15:54 Magnus Damm [this message]
2002-11-14 17:48 ` bi_record and initrd Tom Rini
2002-11-15 12:02 ` Magnus Damm
2002-11-15 17:08 ` Cort Dougan
2002-11-18 8:19 ` Magnus Damm
2002-11-18 17:13 ` Tom Rini
2002-11-19 4:29 ` Murray Jensen
2002-11-18 14:19 ` Tom Rini
2002-11-19 18:11 ` Tom Rini
2002-11-19 18:19 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 21:00 Richard Laing
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=3DD3C747.8B7EE5CD@opensource.se \
--to=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.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.