public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [POWERPC][BUG] ramdisk: u-boot no longer boots a ramdisk with Linux 2.6.27-rc4
Date: Fri, 05 Sep 2008 10:27:38 +0200	[thread overview]
Message-ID: <48C0ED7A.7030000@denx.de> (raw)

Hello Kumar,

I actually trying to boot a Linux 2.6.27-rc4 Kernel with a Ramdisk
and actual u-boot on a MPC82xx based board. And what should I say,
it doesnt work anymore :-(

Reason is the following commit:

http://git.denx.de/?p=u-boot.git;a=commitdiff;h=2a1a2cb6e2b87ee550e6f27b647d23331dfd5e1b#patch3

After this commit, u-boot no longer deletes the mem reservation
for the initrd in Flash, what stops Linux from booting.

So I did the following, but maybe there is a better way for it?

diff --git a/common/fdt_support.c b/common/fdt_support.c
index a7773ab..a69f001 100644
--- a/common/fdt_support.c
+++ b/common/fdt_support.c
@@ -215,8 +215,6 @@ int fdt_chosen(void *fdt, ulong initrd_start, ulong initrd_end, int force)
 		}
 	}

-	fdt_initrd(fdt, initrd_start, initrd_end, force);
-
 #ifdef CONFIG_OF_STDOUT_VIA_ALIAS
 	path = fdt_getprop(fdt, nodeoffset, "linux,stdout-path", NULL);
 	if ((path == NULL) || force)

With this patch Linux boots fine again with the Ramdisk ...

Do you know, why fdt_chosen() is creating a dummy entry for the initrd,
when later fdt_initrd() is again called with the right parameters?

I think, we can drop this!

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

             reply	other threads:[~2008-09-05  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  8:27 Heiko Schocher [this message]
2008-09-05 13:56 ` [U-Boot] [POWERPC][BUG] ramdisk: u-boot no longer boots a ramdisk with Linux 2.6.27-rc4 Kumar Gala
2008-09-05 14:42   ` Heiko Schocher
2008-09-05 16:13     ` Kumar Gala
2008-09-05 16:36       ` Heiko Schocher
2008-09-05 18:02         ` Kumar Gala

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=48C0ED7A.7030000@denx.de \
    --to=hs@denx.de \
    --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