From: Matt Porter <porter@cox.net>
To: Roland Dreier <roland@topspin.com>
Cc: Matt Porter <porter@cox.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony crash fix & 440GP cleanup step one
Date: Wed, 29 May 2002 15:45:51 -0700 [thread overview]
Message-ID: <20020529154551.C3960@home.com> (raw)
In-Reply-To: <523cwcudy1.fsf_-_@topspin.com>; from roland@topspin.com on Tue, May 28, 2002 at 03:04:22PM -0700
On Tue, May 28, 2002 at 03:04:22PM -0700, Roland Dreier wrote:
> This email includes two patches. First, a very small change to
> ocp.h. Somewhere in the recent cleanup, paddr got changed from a
> phys_addr_t to a void *; this doesn't work on 440GP because we have
> 36-bit physical addresses. (You get a machine check when the kernel
> tries to access the ZMII)
>
> Second, the beginning of moving generic IBM 440GP stuff out of
> ebony.c/ebony.h and into platforms/ibm440gp.h. I tested this on my
> Ebony and it boots and runs fine. I didn't go too far because I want
> to make sure everyone feels what I'm doing is the right way to go.
> Please let me know what you think.
Looks great, pushed. There's still more work to do in the includes
but it's a good start. I'm moving the PCIX initialization to a
common library, so don't overlap there if you wander out of
moving headers around.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-29 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 15:58 ZMII Code Panics on 440GP Ebony Venkatesh Rao
2002-05-24 16:40 ` Roland Dreier
2002-05-24 19:20 ` Matt Porter
2002-05-24 19:17 ` Roland Dreier
2002-05-24 20:47 ` Matt Porter
2002-05-28 22:04 ` Ebony crash fix & 440GP cleanup step one Roland Dreier
2002-05-29 22:45 ` Matt Porter [this message]
2002-05-30 23:00 ` Roland Dreier
2002-06-04 0:44 ` A few more PPC440GP/Ebony cleanups Roland Dreier
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=20020529154551.C3960@home.com \
--to=porter@cox.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=roland@topspin.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).