From: Jon Loeliger <jdl@freescale.com>
To: Martyn Welch <martyn.welch@gefanuc.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/2] powerpc: Board support for GE Fanuc SBC610
Date: Thu, 21 Aug 2008 13:17:55 -0500 [thread overview]
Message-ID: <48ADB153.20208@freescale.com> (raw)
In-Reply-To: <20080821144144.fed06908.martyn.welch@gefanuc.com>
Martyn Welch wrote:
> Support for the SBC610 VPX Single Board Computer from GE Fanuc (PowerPC
> MPC8641D).
>
> This is the basic board support for GE Fanuc's SBC610, a 6U single board
> computer, based on Freescale's MPC8641D.
>
> Signed-off-by: Martyn Welch <martyn.welch@gefanuc.com>
> ---
>
> arch/powerpc/boot/dts/gef_sbc610.dts | 268 ++++++++++++++++++++++++++++++
> arch/powerpc/platforms/86xx/Kconfig | 9 +
> arch/powerpc/platforms/86xx/Makefile | 1
> arch/powerpc/platforms/86xx/gef_sbc610.c | 187 +++++++++++++++++++++
> 4 files changed, 464 insertions(+), 1 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/gef_sbc610.dts
> create mode 100644 arch/powerpc/platforms/86xx/gef_sbc610.c
>
>
> + soc8641@fef00000 {
No "8641" in this name, please.
Oh, and drop the ""32-bit" in the CPU sections too.
> + ecc@2000 {
> + device_type = "dram-controller";
Hmmm, I suspect that should be dropped.
> + compatible = "mpc86xx";
And that changed to indicate some form of controller thing.
Using "mpc86xx" here is just not right at all.
> +
> + serial0: serial@4500 {
> + cell-index = <0>;
> + device_type = "serial";
> + compatible = "ns16550";
> + reg = <0x00004500 0x00000100>;
> + clock-frequency = <0>;
> + interrupts = <0x2a 0x2>;
> + interrupt-parent = <&mpic>;
> + };
> +
> + serial1: serial@4600 {
> + cell-index = <1>;
> + device_type = "serial";
> + compatible = "ns16550";
> + reg = <0x00004600 0x00000100>;
> + clock-frequency = <0>;
> + interrupts = <0x1c 0x2>;
> + interrupt-parent = <&mpic>;
> + };
There's some form of indenting issue there...
> + mpic: pic@40000 {
> + clock-frequency = <0>;
> + interrupt-controller;
> + #address-cells = <0>;
> + #interrupt-cells = <2>;
> + reg = <0x00040000 0x00040000>;
> + built-in;
> + compatible = "chrp,open-pic";
> + device_type = "open-pic";
> + big-endian;
IIRC, we dropped "big-endian" too. (?)
> diff --git a/arch/powerpc/platforms/86xx/gef_sbc610.c b/arch/powerpc/platforms/86xx/gef_sbc610.c
> new file mode 100644
> index 0000000..6b92876
> --- /dev/null
> +++ b/arch/powerpc/platforms/86xx/gef_sbc610.c
> @@ -0,0 +1,187 @@
> +
> +/*
> + * Based on: mpc86xx_hpcn.c
> + *
> + * MPC86xx HPCN board specific routines
> + *
> + * Recode: ZHANG WEI <wei.zhang@freescale.com>
> + * Initial author: Xianghua Xiao <x.xiao@freescale.com>
> + *
> + * Copyright 2006 Freescale Semiconductor Inc.
> + *
> + */
This seems misleading some. Sure, state your attributions
and derivation sources, but this also still looks like it
is stating that it *is* the MPC86xx HPCN board code.
Thanks,
jdl
next prev parent reply other threads:[~2008-08-21 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080821133852.17201.3862.stgit@welchma.Radstone.Local>
2008-08-21 13:41 ` [PATCH 1/2] powerpc: Board support for GE Fanuc SBC610 Martyn Welch
2008-08-21 18:17 ` Jon Loeliger [this message]
2008-08-21 18:38 ` Scott Wood
2008-08-21 19:54 ` Kumar Gala
2008-08-21 13:41 ` [PATCH 2/2] powerpc: Default configuration " Martyn Welch
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=48ADB153.20208@freescale.com \
--to=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=martyn.welch@gefanuc.com \
--cc=paulus@samba.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).