linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: fix up the bd_info address
Date: Fri, 27 Oct 2006 00:17:02 +0400	[thread overview]
Message-ID: <20061027001702.4da5f5b0@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 317 bytes --]

Hi,

The patch is attached. It is applied after Matt's bootm stuff. I was going to send it through u-boot list when
all the things around FDT will arrive there. It used to fix the problem booting the bd_t kernel on FDT u-boot.

Just as reference for now.

Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: fix_bd_info_address.patch --]
[-- Type: text/x-patch; name=fix_bd_info_address.patch, Size: 783 bytes --]

Patch fixes the address of the board info passed to kernel when OF tree is disabled.

---

 common/cmd_bootm.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c
index f1c0eb4..eb59817 100644
--- a/common/cmd_bootm.c
+++ b/common/cmd_bootm.c
@@ -836,8 +836,12 @@ #endif
 	(*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end);
 
 #else
-	ft_setup(of_flat_tree, kbd, initrd_start, initrd_end);
-	/* ft_dump_blob(of_flat_tree); */
+	if (getenv("disable_of") != NULL)
+		of_flat_tree = kbd;
+	else {
+		ft_setup(of_flat_tree, kbd, initrd_start, initrd_end);
+		/* ft_dump_blob(of_flat_tree); */
+	}
 
 #if defined(CFG_INIT_RAM_LOCK) && !defined(CONFIG_E500)
 	unlock_ram_in_cache();

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2006-10-26 20:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061027001702.4da5f5b0@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).