linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: LiuTao <tliu@ict.ac.cn>
To: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>,
	LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Do me a favor about gunzip()
Date: Fri, 14 Jan 2000 12:51:23 +0800	[thread overview]
Message-ID: <387EAB4B.B9FFF19E@ict.ac.cn> (raw)


Hi:

If you have a board with MPC860 and you ported Linux to your board
successfully, do me a favor please.

Do following steps:
1. Use objdump to find out the location of identify_machine() in
vmlinux,
in my vmlinux, the location is 0xC00C8984.
2. Setup a break point after gunzip() in decompress_kernel().
3. Check the location(0x000C8984) of identify_machine(), is the
contents correct?

By the way, what kind of debug tool are you using when you port and
debug Linux on your PowerPC board?

Thanks!

LiuTao

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

                 reply	other threads:[~2000-01-14  4:51 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=387EAB4B.B9FFF19E@ict.ac.cn \
    --to=tliu@ict.ac.cn \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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;
as well as URLs for NNTP newsgroup(s).