From: LiuTao <tliu@ict.ac.cn>
To: "Shuangjun Zhu (r44089)" <r44089@email.sps.mot.com>,
LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ;X84: problem with gunzip()
Date: Mon, 10 Jan 2000 18:14:39 +0800 [thread overview]
Message-ID: <3879B10F.D6C21C0F@ict.ac.cn> (raw)
In-Reply-To: 003001bf5b47$6aeebe20$73f102de@sjzhu
You mean the extenal interrupt enable bit?
It's really disabled before gunzip.
LiuTao
Shuangjun Zhu wrote:
>
> Before you gunzip the kernel, clear the interrupt bit in the
> machine status register.
>
> -----Original Message-----
> From: LiuTao <tliu@ict.ac.cn>
> To: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>; linuxppc-embedded@lists.linuxppc.org
> <linuxppc-embedded@lists.linuxppc.org>
> Date: Monday, January 10, 2000 4:43 PM
> Subject: problem with gunzip()
>
> >
> >Hi
> >
> >When I ported linux to a board with MPC860, 16M RAM and 2M Flash,
> >I met a problem.
> >After the program gunzip()(misc.c) the vmlinux image to address 0x0,
> >the contents from 0x0 to IMAGE_SIZE should be as same as that in
> >linux/vmlinux, right? I found that they are not same. Only from 0x0
> >to about 0xb500, they are same.
> >I don't think gunzip() has any problem.
> >Do you have any suggestions?
> >Thanks!
> >
> >LiuTao
> >
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-01-10 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 8:48 ~{;X84~}: problem with gunzip() Shuangjun Zhu
2000-01-10 10:14 ` LiuTao [this message]
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=3879B10F.D6C21C0F@ict.ac.cn \
--to=tliu@ict.ac.cn \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=r44089@email.sps.mot.com \
/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).