linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Stephen N Chivers <schivers@csc.com.au>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
	Chris Proctor <cproctor@csc.com.au>
Subject: Re: [RFC PATCH 1/1] powerpc/embedded6xx: Add support for Motorola/Emerson MVME5100.
Date: Thu, 8 Aug 2013 10:30:53 -0500	[thread overview]
Message-ID: <B7B7FD2F-8272-487C-B946-154107EF7C09@kernel.crashing.org> (raw)
In-Reply-To: <OFBCFBBD51.E4ECB0DF-ONCA257BC0.0083C866-CA257BC1.0000531E@csc.com>


On Aug 7, 2013, at 7:03 PM, Stephen N Chivers wrote:

> Add support for the Motorola/Emerson MVME5100 Single Board Computer.
>=20
> The MVME5100 is a 6U form factor VME64 computer with:
>=20
>        - A single MPC7410 or MPC750 CPU
>        - A HAWK Processor Host Bridge (CPU to PCI) and
>          MultiProcessor Interrupt Controller (MPIC)
>        - Up to 500Mb of onboard memory
>        - A M48T37 Real Time Clock (RTC) and Non-Volatile Memory chip
>        - Two 16550 compatible UARTS
>        - Two Intel E100 Fast Ethernets
>        - Two PCI Mezzanine Card (PMC) Slots
>        - PPCBug Firmware
>=20
> The HAWK PHB/MPIC is compatible with the MPC10x devices.
>=20
> There is no onboard disk support. This is usually provided by =
installing a=20
> PMC
> in first PMC slot.
>=20
> This patch revives the board support, it was present in early 2.6
> series kernels. The board support in those days was by Matt Porter of
> MontaVista Software.
>=20
> CSC Australia has around 31 of these boards in service. The kernel in =
use
> for the boards is based on 2.6.31. The boards are operated without =
disks
> from a file server.=20
>=20
> This patch is based on linux-3.11-rc4 and has been boot tested.
>=20
> Signed-off-by: Stephen Chivers <schivers@csc.com>
> ---
> arch/powerpc/boot/dts/mvme5100.dts            |  195 ++
> arch/powerpc/boot/mvme5100.c                  |   28 +
> arch/powerpc/configs/mvme5100_defconfig       | 2597=20
> +++++++++++++++++++++++++
> arch/powerpc/platforms/embedded6xx/mvme5100.c |  288 +++
> 4 files changed, 3108 insertions(+), 0 deletions(-)

Please look at fixing the white space issues you seem to have throughout =
this patch.

Also, we don't take full defconfigs in the tree, look at 'make =
savedefconfig'

- k

  reply	other threads:[~2013-08-08 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  0:03 [RFC PATCH 1/1] powerpc/embedded6xx: Add support for Motorola/Emerson MVME5100 Stephen N Chivers
2013-08-08 15:30 ` Kumar Gala [this message]
2013-08-08 18:07   ` Scott Wood
2013-08-12 21:57     ` Stephen N Chivers
2013-08-12 22:04       ` Scott Wood
2013-08-18 20:58         ` Stephen N Chivers
2013-08-20  0:44           ` Scott Wood
2013-08-20  4:05             ` Stephen N Chivers
2013-08-12 21:06   ` Stephen N Chivers
2013-08-09  1:35 ` Scott Wood
2013-08-20  2:28   ` Stephen N Chivers
2013-08-20 23:20     ` Scott Wood
2013-08-22  0:58       ` Stephen N Chivers
     [not found]       ` <OFA6564D85.57B12E50-ONCA257BCF.00042385-CA257BCF.00055385@LocalDomain>
2013-08-29 22:36         ` Stephen N Chivers

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=B7B7FD2F-8272-487C-B946-154107EF7C09@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=cproctor@csc.com.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=schivers@csc.com.au \
    /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).