From: Wolfgang Denk <wd@denx.de>
To: bart@ardistech.com
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>,
dmalek@jlc.net
Subject: Re: MP8xx: not initialized CPM RAM crash
Date: Fri, 03 May 2002 08:40:33 +0200 [thread overview]
Message-ID: <20020503064038.64A6111952@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 03 May 2002 07:51:23 +0200." <3CD2255B.330FA4E4@ardistech.com>
In message <3CD2255B.330FA4E4@ardistech.com> you wrote:
>
> I found in ./drivers/i2c/i2c-rpx.c in rpx_iic_init the structure member
> ii->iic_rpbase != 0. Very likely because ppcboot uses this area as initial
> stack. This causes the kernel to get a machine check during i2c init. Should
> the CPM RAM not be zero'd somewhere during kernel boot?
Which kernel version are you talking about?
I think we fixed this in our version of the 8xx I2C driver long ago.
I don't think that the whole CPM RAM should be zeroed; it's
sufficient to correctly initialize the necessary fields.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
They weren't that important. They were merely at the top. The people
who really run organizations are usually found several levels down,
where it's still possible to get things done.
- Terry Pratchett, _Small Gods_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-03 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 5:51 MP8xx: not initialized CPM RAM crash bart
2002-05-03 6:40 ` Wolfgang Denk [this message]
2002-05-03 7:25 ` bart
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=20020503064038.64A6111952@denx.denx.de \
--to=wd@denx.de \
--cc=bart@ardistech.com \
--cc=dmalek@jlc.net \
--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).