[PATCH] powerpc: Don't try OPAL takeover on old 970 blades

The firmware on old 970 blades supports some kind of takeover called "TNK takeover" which will crash if we try to probe for OPAL takeover, so don't do it. Signed-off-by: Benjamin Herrenschmidt --- diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c index e96f5d0..b4fa6

powerpc: Fix device-tree matching for Apple U4 bridge

Apple Quad G5 has some oddity in it's device-tree which causes the new generic matching code to fail to relate nodes for PCI-E devices below U4 with their respective struct pci_dev. This breaks graphics on those machines among others. This fixes it using a quirk which copies the node pointer from

Re: [PATCH REPOST] perf event, POWER 6: L1 cache read and write access event code fix]

On Wed, Sep 28, 2011 at 02:23:33PM -0700, Carl E. Love wrote: > The current L1 cache read event code 0x80082 only counts for thread 0. The > event code 0x280030 should be used to count events on thread 0 and 1. The > patch fixes the event code for the L1 cache read. > > The current L1 cache write

[PATCH 4/4] powerpc/fsl: Document rapidio node binding-information

This document is created for powerpc rapidio and rmu nodes in dts file. These nodes can support two rapidio ports and message units. In addition, It explicates the properties and gives examples about rapidio and rmu nodes. Signed-off-by: Li Yang Signed-off-by: Jin Qing Signed-off-by: Liu Gang

[PATCH 2/4] fsl-rio: Add two ports and rapidio message units support

Usually, freescale rapidio endpoint can support one 1X or two 4X LP-Serial link interfaces, and rapidio message transactions can be implemented by two message units. This patch adds the support of two rapidio ports and initializes message unit 0 and message unit 1. And these ports and message un

[PATCH 3/4] p4080ds-dts: Add two rapidio ports and message units support

Add two message units and number of ports according to the p4080 reference manual. Signed-off-by: Li Yang Signed-off-by: Jin Qing Signed-off-by: Liu Gang --- arch/powerpc/boot/dts/p4080ds.dts |4 +- arch/powerpc/boot/dts/p4080si.dtsi | 37 +++ 2 files ch

Re: [RFC] CONFIG_RELOCATABLE : __va() & __pa() definitions

On Tue, 2011-09-27 at 17:54 +0530, Suzuki Poulose wrote: > Hi, > > I am working on enabling CONFIG_RELOCATABLE for PPC44x Embedded PowerPC > boards as a foundation to enable CONFIG_CRASH_DUMP. After a discussion > on the linux-ppcdev we decided that we will follow the 'processing > relocation e

Re: linux-next: build failure after merge of the akpm tree

On Wed, 28 Sep 2011 19:22:20 +1000 Stephen Rothwell wrote: > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from arch/powerpc/boot/stdio.c:12:0: > arch/powerpc/boot/stdio.h:10:17: error: expected declaration specifiers or

[PATCH REPOST] perf event, POWER 6: L1 cache read and write access event code fix]

Ben, Paul: I posted this patch to lkml but did not copy the linuxppc-...@ozlabs.org mailing list. Carl Love - The current L1 cache read event code 0x80082 only counts for thread 0. The event code 0x280030 s

Re: Handling multiple GPIO controllers in 8xxx GPIO driver

On Tue, Sep 27, 2011 at 1:29 PM, Grant Likely wrote: > The solution is to make the gpio driver register as a regular > interrupt handler, and not as a chained handler. I was wondering about that. What exactly is a chained handler? How is it different from a regular handler? -- Timur Tabi Lin

linux-next: build failure after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from arch/powerpc/boot/stdio.c:12:0: arch/powerpc/boot/stdio.h:10:17: error: expected declaration specifiers or '...' before numeric constant arch/powerpc/boot/stdio.h:10