public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
	Josh Boyer <jwboyer@gmail•com>
Cc: LinuxPPC-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: Add support for the currituck 476 platform from IBM (v2)
Date: Thu, 1 Dec 2011 18:43:08 +1100	[thread overview]
Message-ID: <20111201074307.GK15560@thor.bakeyournoodle.com> (raw)
In-Reply-To: <1322725164-4391-1-git-send-email-tony@bakeyournoodle.com>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

On Thu, Dec 01, 2011 at 06:39:16PM +1100, Tony Breeds wrote:
> Patches 1 to 3
>         Modify the 44x PCI code to work with 476fpe/currituck.
> Patch 4
>        	Is an old patch by Christoph Egger that fell through the cracks somehow.
> Patches 5 and 6
>         Modify the bootwrapper to handle 476fpe/currituck
> Patch 7
>        	The SoC support.
> Patch 8
>        	The currituck board support.

Sorry I forgot the diffstat

 arch/powerpc/boot/Makefile                   |    5 +-
 arch/powerpc/boot/dcr.h                      |    6 +
 arch/powerpc/boot/div64.S                    |   52 ++++++
 arch/powerpc/boot/dts/currituck.dts          |  237 ++++++++++++++++++++++++++
 arch/powerpc/boot/treeboot-currituck.c       |  119 +++++++++++++
 arch/powerpc/boot/wrapper                    |    3 +
 arch/powerpc/configs/44x/currituck_defconfig |  110 ++++++++++++
 arch/powerpc/include/asm/reg.h               |    1 +
 arch/powerpc/kernel/cputable.c               |   14 ++
 arch/powerpc/kernel/head_44x.S               |    2 +
 arch/powerpc/mm/44x_mmu.c                    |    4 -
 arch/powerpc/platforms/44x/Kconfig           |   14 ++
 arch/powerpc/platforms/44x/Makefile          |    1 +
 arch/powerpc/platforms/44x/currituck.c       |  204 ++++++++++++++++++++++
 arch/powerpc/sysdev/ppc4xx_pci.c             |   85 +++++++++-
 arch/powerpc/sysdev/ppc4xx_pci.h             |    7 +
 16 files changed, 851 insertions(+), 13 deletions(-)

Yours Tony

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2011-12-01  7:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  7:39 Add support for the currituck 476 platform from IBM (v2) Tony Breeds
2011-12-01  7:39 ` [PATCH 1/8] 44x/pci: Use PCI_BASE_ADDRESS_MEM_PREFETCH rather than magic value Tony Breeds
2011-12-01  7:39 ` [PATCH 2/8] 44x/pci: Add a want_sdr flag into ppc4xx_pciex_hwops Tony Breeds
2011-12-02 20:57   ` Benjamin Herrenschmidt
2011-12-01  7:39 ` [PATCH 3/8] 44x/pci: Setup the dma_window properties for each pci_controller Tony Breeds
2011-12-01  7:39 ` [PATCH 4/8] 44x: Removing dead CONFIG_PPC47x Tony Breeds
2011-12-01  7:39 ` [PATCH 5/8] powerpc/boot: Add extended precision shifts to the boot wrapper Tony Breeds
2011-12-01  7:39 ` [PATCH 6/8] powerpc/boot: Add mfdcrx Tony Breeds
2011-12-01  7:39 ` [PATCH 7/8] 44x/476fpe: Add 476fpe SoC code Tony Breeds
2011-12-02 20:58   ` Benjamin Herrenschmidt
2011-12-03 10:11     ` Tony Breeds
2011-12-03 13:33       ` Josh Boyer
2011-12-03 21:52         ` Tony Breeds
2011-12-01  7:39 ` [PATCH 8/8] 44x/currituck: Add support for the new IBM currituck platform Tony Breeds
2011-12-01  7:43 ` Tony Breeds [this message]

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=20111201074307.GK15560@thor.bakeyournoodle.com \
    --to=tony@bakeyournoodle$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=jwboyer@gmail$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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