public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel•crashing.org>
To: Magnus Damm <damm@opensource•se>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: bi_record and initrd
Date: Thu, 14 Nov 2002 10:48:07 -0700	[thread overview]
Message-ID: <20021114174807.GC605@opus.bloom.county> (raw)
In-Reply-To: <3DD3C747.8B7EE5CD@opensource.se>


On Thu, Nov 14, 2002 at 04:54:47PM +0100, Magnus Damm wrote:

> 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?

Can you give more information about where everything is loaded up at?  I
thought this was a non-issue, but it's been a while since I tested
initrds.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-11-14 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14 15:54 bi_record and initrd Magnus Damm
2002-11-14 17:48 ` Tom Rini [this message]
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=20021114174807.GC605@opus.bloom.county \
    --to=trini@kernel$(echo .)crashing.org \
    --cc=damm@opensource$(echo .)se \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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