From: "Mark A. Greer" <mgreer@mvista.com>
To: James Chapman <jchapman@katalix.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 2.6.11-rc4] ppc: add support for Radstone ppc7d boards
Date: Thu, 03 Mar 2005 10:58:17 -0700 [thread overview]
Message-ID: <42275039.7000702@mvista.com> (raw)
In-Reply-To: <4224C285.6000409@katalix.com>
James Chapman wrote:
> Revised patch for Radstone PPC7D board support.
>
> Signed-off-by: James Chapman <jchapman@katalix.com>
>
> - use mv64x60_set_bus() to setup for PCI scans rather than
> writing to chip P2P_CONFIG registers directly.
Looks good, James, except for a couple minor things. If/when you
address the comments, please resubmit the entire patch with a proper
description so I can forward it on -- http://linux.yyz.us/patch-format.html
Thanks,
Mark
--
> diff -Nru a/arch/ppc/platforms/radstone_ppc7d.c
b/arch/ppc/platforms/radstone_ppc7d.c
> +#if defined(CONFIG_SERIAL_MPSC_CONSOLE)
> + mv64x60_mpsc_init(port, uart);
Don't you mean "mv64x60_progress_init( <base> );" ?
> diff -Nru a/arch/ppc/platforms/radstone_ppc7d.h
b/arch/ppc/platforms/radstone_ppc7d.h
>+#define PPC7D_MV64360_REG_BASE 0xfef00000
You don't really need this b/c CONFIG_MV64X60_NEW_BASE should have the
correct value.
next prev parent reply other threads:[~2005-03-03 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 17:55 [PATCH 2.6.11-rc4] ppc: add support for Radstone ppc7d boards James Chapman
2005-02-28 20:53 ` Mark A. Greer
2005-02-28 21:31 ` James Chapman
2005-02-28 22:13 ` James Chapman
2005-02-28 22:24 ` Mark A. Greer
2005-03-01 19:29 ` James Chapman
2005-03-03 17:58 ` Mark A. Greer [this message]
2005-03-03 22:06 ` [PATCH 2.6.11-rc5] ppc32: add Radstone PPC7D platform support James Chapman
2005-03-03 22:50 ` James Chapman
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=42275039.7000702@mvista.com \
--to=mgreer@mvista.com \
--cc=jchapman@katalix.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.