LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: THEDREAM@chollian.net
To: cinpet@adaptivemicro.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem during decompressing kernel routine
Date: Tue, 11 Sep 2001 09:20:51 +0900	[thread overview]
Message-ID: <200109110019.JAA20501@ldap.dacom.co.kr> (raw)


I donot know exact answer. because I donot know your situation such as which CPU
you use, how you port Linux and so on.

So I just guess the reason.

I sometimes saw the same message that you see.

In this case, I could port the Kernel when I checked IMMR values in the Kernel.

It's an assumption.

Good Luck. Bye ~~~


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

             reply	other threads:[~2001-09-11  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11  0:20 THEDREAM [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-10 15:08 Problem during decompressing kernel routine Cindy Peters
2001-09-10 14:20 Cindy Peters
2001-09-10 11:09 ` Matt Porter

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=200109110019.JAA20501@ldap.dacom.co.kr \
    --to=thedream@chollian.net \
    --cc=cinpet@adaptivemicro.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox