linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Chenfeng Zhou" <ini_autumn@163.com>
To: linuxppc-embedded@ozlabs.org
Subject: [ppc44x-patch] Is this a bug?
Date: Fri, 27 May 2005 12:08:26 +0800 (CST)	[thread overview]
Message-ID: <42969D3A.000005.25949@m217.163.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

In linux-2.4.25 source tree, maybe there's something wrong with the boot process of 
ppc44x cpu.

In arch/ppc/boot/common/relocate.S, we decompress the kernel to address 0, then jump
there to do real boot job (arch/ppc/kernel/head_44x.S). But the last expression is `ba 0x000c'.

Actually there's only one nop at the begining of head_44x.S, so the expression should
be `ba 0x0004' for ppc-44x. But for compatibility, i think it should be `ba 0x0',
because there's different number of 'nops' in head.S for different cpus.

Actually, in linux-2.4.26, linux-2.4.30, i also found the same problem.
but in linux-2.6, it seems solved already.

Thank you.

patch below:

diff -rNu linux-2.4.25/arch/ppc/boot/common/relocate.S linux-2.4.25.me/arch/ppc/boot/common/relocate.S
--- linux-2.4.25/arch/ppc/boot/common/relocate.S        2003-08-25 19:44:40.000000000 +0800
+++ linux-2.4.25.me/arch/ppc/boot/common/relocate.S     2005-05-27 12:07:05.000000000 +0800
@@ -203,6 +203,7 @@
         * three instructions are 'nop' since we
         * sometimes overwrite them).
         */
-       ba      0x000c
+       #ba     0x000c
+       ba 0x0

        .comm   .stack,4096*2,4



[-- Attachment #2: Type: text/html, Size: 2001 bytes --]

                 reply	other threads:[~2005-05-27  4:24 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=42969D3A.000005.25949@m217.163.com \
    --to=ini_autumn@163.com \
    --cc=linuxppc-embedded@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).