Re: [git pull] Please pull powerpc.git next branch (updated)

2011-06-28 Thread Kumar Gala
[ pulled in a few additional patches, and fixed the fsl_pci change to build on ppc64 platforms as well ] The following changes since commit dc28518f7d7dfd93cd44edb44f9b8e961f5a5c1b: powerpc: Fix doorbell type shift (2011-06-20 11:21:48 +1000) are available in the git repository at:

[PATCH] powerpc/85xx: Add p2040 RDB board support

2011-06-28 Thread Mingkai Hu
P2040RDB Specification: --- 2Gbyte unbuffered DDR3 SDRAM SO-DIMM(64bit bus) 128 Mbyte NOR flash single-chip memory 256 Kbit M24256 I2C EEPROM 16 Mbyte SPI memory SD connector to interface with the SD memory card dTSEC1: connected to the Vitesse SGMII PHY (VSC8221) dTSEC2:

Re: [BUG?]3.0-rc4+ftrace+kprobe: set kprobe at instruction 'stwu' lead to system crash/freeze

2011-06-28 Thread Ananth N Mavinakayanahalli
On Mon, Jun 27, 2011 at 03:31:05PM +0530, Ananth N Mavinakayanahalli wrote: On Sun, Jun 26, 2011 at 11:47:13PM +0900, Masami Hiramatsu wrote: (2011/06/24 19:29), Steven Rostedt wrote: On Fri, 2011-06-24 at 17:21 +0800, Yong Zhang wrote: Hi, When I use kprobe to do something, I found

Re: [PATCH] powerpc, 460gt: Add 460gt as compatible in the check for 460ex-compatible crypto

2011-06-28 Thread Josh Boyer
On Fri, Jun 24, 2011 at 04:14:07AM +0200, Segher Boessenkool wrote: -       if (of_find_compatible_node(NULL, NULL, amcc,ppc460ex-crypto)) { +       if (of_find_compatible_node(NULL, NULL, amcc,ppc460ex-crypto) || +           of_find_compatible_node(NULL, NULL, amcc,ppc460gt-crypto)) { If the

Re: [PATCH] powerpc, 460gt: Add 460gt as compatible in the check for 460ex-compatible crypto

2011-06-28 Thread Mike Williams
On Tue, Jun 28, 2011 at 7:48 AM, Josh Boyer jwbo...@linux.vnet.ibm.com wrote: On Fri, Jun 24, 2011 at 04:14:07AM +0200, Segher Boessenkool wrote: -       if (of_find_compatible_node(NULL, NULL, amcc,ppc460ex-crypto)) { +       if (of_find_compatible_node(NULL, NULL, amcc,ppc460ex-crypto) || +    

Please pull 'next' branch of 4xx tree

2011-06-28 Thread Josh Boyer
Hi Ben, A small pull request to add some DTS entries to bind to the new HW RNG driver for 4xx. I know Eric has the Bluegene stuff being worked on, and there are patches from Michal Simek for relocatable kernel support out for RFC. I need to review those a bit more closely, so they will probably

Re: Bug#630845: linux-image-2.6.39-2-powerpc: CHRP Pegasos2 boot failure

2011-06-28 Thread Gabriel Paubert
On Sun, Jun 26, 2011 at 11:14:13PM +0100, Ben Hutchings wrote: On Thu, 2011-06-23 at 20:36 +0800, Andrew Buckeridge wrote: Package: linux-image-3.0.0-rc3-powerpc Version: 3.0.0~rc3-1~experimental.1 On Wed, 22 Jun 2011 04:01:38 +0100 Ben Hutchings b...@decadent.org.uk wrote:

Re: [BUG?]3.0-rc4+ftrace+kprobe: set kprobe at instruction 'stwu' lead to system crash/freeze

2011-06-28 Thread Steven Rostedt
On Tue, 2011-06-28 at 16:11 +0530, Ananth N Mavinakayanahalli wrote: My access to a 32bit powerpc box is very limited. Also, embedded powerpc has had issues with gcc-4.6 while gcc-4.5 worked fine. I'd work to debug this too, but I don't have access to a 32bit ppc either. Although I've been

[PATCH] dtc: Remove unused variable in flat_read_mem_reserve

2011-06-28 Thread Josh Boyer
The *p variable is declared and used to save inb-ptr, however p is later never used. This has been the case since commit 6c0f3676 and can lead to build failures with -Werror=unused-but-set-variable: flattree.c: In function 'flat_read_mem_reserve': flattree.c:700:14: error:

Re: [PATCH] dtc: Remove unused variable in flat_read_mem_reserve

2011-06-28 Thread Josh Boyer
On Tue, Jun 28, 2011 at 09:42:53AM -0400, Josh Boyer wrote: The *p variable is declared and used to save inb-ptr, however p is later never used. This has been the case since commit 6c0f3676 and can lead to build failures with -Werror=unused-but-set-variable: flattree.c: In function

[PATCH v2] dtc: Remove unused variable in flat_read_mem_reserve

2011-06-28 Thread Josh Boyer
The *p variable is declared and used to save inb-ptr, however p is later never used. This has been the case since commit 6c0f3676 and can lead to build failures with -Werror=unused-but-set-variable: flattree.c: In function 'flat_read_mem_reserve': flattree.c:700:14: error:

[PATCH] dtc: Remove unused check variable

2011-06-28 Thread Josh Boyer
Commit 376ab6f2 removed the old style check functionality from DTC, however the check option and variable were not removed. This leads to build failures when -Werror=unused-but-set-variable is specified: dtc.c: In function 'main': dtc.c:102:17: error: variable 'check' set but not

Re: [PATCH v13 09/10] USB ppc4xx: Add Synopsys DWC OTG driver kernel configuration and Makefile

2011-06-28 Thread Mike Williams
On Sun, Apr 03, 2011 at 04:17:24PM -0700, tmarri at apm.com wrote: +choice + prompt DWC Mode Selection + depends on USB_DWC_OTG + default DWC_HOST_ONLY + help +  Select the DWC Core in OTG, Host only, or Device only mode. + +config DWC_HOST_ONLY + bool DWC Host Only Mode + +config

RE: [PATCH 2/2] mtd/nand : workaround for Freescale FCM to supportlarge-page Nand chip

2011-06-28 Thread Mike Hench
Any boot ideas ? Will the FCM load 2k and run it? Thanks for any insight you might have. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: [PATCH] powerpc/timebase_read: don't return time older than cycle_last

2011-06-28 Thread Scott Wood
On Tue, 28 Jun 2011 10:45:43 +1000 Benjamin Herrenschmidt b...@kernel.crashing.org wrote: On Mon, 2011-06-27 at 16:56 -0500, Scott Wood wrote: As is done in read_tsc() on x86, make sure that we don't return a timebase value smaller than cycle_last, which can happen on SMP if the timebases

Re: [PATCH 2/2] mtd/nand : workaround for Freescale FCM to supportlarge-page Nand chip

2011-06-28 Thread Scott Wood
On Tue, 28 Jun 2011 11:35:12 -0400 Mike Hench mhe...@elutions.com wrote: Any boot ideas ? Will the FCM load 2k and run it? The 4K boot region will have to be split over pages 0 and 2 (2k view) or the first half of pages 0 and 1 (4k view). -Scott

[PATCH 1/5] fs/hugetlbfs/inode.c: Fix pgoff alignment checking on 32-bit

2011-06-28 Thread Becky Bruce
From: Becky Bruce bec...@kernel.crashing.org This: vma-vm_pgoff ~(huge_page_mask(h) PAGE_SHIFT) is incorrect on 32-bit. It causes us to the pgoff with something that looks like this (for a 4m hugepage): 0xfff003ff. The mask should be flipped and *then* shifted, to give you 0x_03fff.

[PATCH 2/5] hugetlb: add phys addr to struct huge_bootmem_page

2011-06-28 Thread Becky Bruce
From: Becky Bruce bec...@kernel.crashing.org This is needed on HIGHMEM systems - we don't always have a virtual address so store the physical address and map it in as needed. Signed-off-by: Becky Bruce bec...@kernel.crashing.org --- include/linux/hugetlb.h |3 +++ mm/hugetlb.c|

[PATCH 3/5] powerpc: mem_init should call memblock_is_reserved with phys_addr_t

2011-06-28 Thread Becky Bruce
From: Becky Bruce bec...@kernel.crashing.org This has been broken for a while but hasn't been an issue until now because nobody was reserving regions at high addresses. Signed-off-by: Becky Bruce bec...@kernel.crashing.org --- arch/powerpc/mm/mem.c |3 ++- 1 files changed, 2 insertions(+),

[PATCH 4/5] powerpc: Create next_tlbcam_idx percpu variable for FSL_BOOKE

2011-06-28 Thread Becky Bruce
From: Becky Bruce bec...@kernel.crashing.org This is used to round-robin TLBCAM entries. Signed-off-by: Becky Bruce bec...@kernel.crashing.org --- arch/powerpc/include/asm/mmu.h |5 + arch/powerpc/kernel/smp.c |4 arch/powerpc/mm/mem.c |9 +

[PATCH 5/5] powerpc: Hugetlb for BookE

2011-06-28 Thread Becky Bruce
From: Becky Bruce bec...@kernel.crashing.org Enable hugepages on Freescale BookE processors. This allows the kernel to use huge TLB entries to map pages, which can greatly reduce the number of TLB misses and the amount of TLB thrashing experienced by applications with large memory footprints.

Re: [PATCH 2/5] hugetlb: add phys addr to struct huge_bootmem_page

2011-06-28 Thread Benjamin Herrenschmidt
On Tue, 2011-06-28 at 14:54 -0500, Becky Bruce wrote: struct page *alloc_huge_page_node(struct hstate *h, int nid); diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 6402458..2db81ea 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -1105,8 +1105,14 @@ static void __init

Re: [PATCH v4]PPC4xx: Adding PCI(E) MSI support

2011-06-28 Thread Ayman El-Khashab
On Thu, May 26, 2011 at 03:24:44PM +1000, Benjamin Herrenschmidt wrote: Please check the result and send any fixup patch that might be necessary. +static int ppc4xx_setup_pcieh_hw(struct platform_device *dev, +struct resource res, struct ppc4xx_msi *msi) +{

Re: [PATCH v4]PPC4xx: Adding PCI(E) MSI support

2011-06-28 Thread Benjamin Herrenschmidt
On Tue, 2011-06-28 at 17:31 -0500, Ayman El-Khashab wrote: +static int ppc4xx_setup_pcieh_hw(struct platform_device *dev, +struct resource res, struct ppc4xx_msi *msi) +{ + snip + + msi-msi_dev = of_find_node_by_name(NULL, ppc4xx-msi); +

Re: [PATCH] powerpc/timebase_read: don't return time older than cycle_last

2011-06-28 Thread Benjamin Herrenschmidt
On Tue, 2011-06-28 at 11:14 -0500, Scott Wood wrote: You are applying a bandage on a wooden leg here userspace (vDSO) will see the time going backward if you aren't well synchronized as well, so you're stuffed anyways. Sure -- but we should avoid turning a slight backwards drift into

Re: [PATCH] powerpc/timebase_read: don't return time older than cycle_last

2011-06-28 Thread Scott Wood
On Wed, 29 Jun 2011 09:25:08 +1000 Benjamin Herrenschmidt b...@kernel.crashing.org wrote: On Tue, 2011-06-28 at 11:14 -0500, Scott Wood wrote: You are applying a bandage on a wooden leg here userspace (vDSO) will see the time going backward if you aren't well synchronized as well,

Re: [PATCH] powerpc/timebase_read: don't return time older than cycle_last

2011-06-28 Thread Benjamin Herrenschmidt
Ok two things. One is first fix the comments then to stop mentioning TSC :-) Doh, sorry... Second is, I still don't think it's right. There's an expectation on powerpc that the timebase works properly. If not, you have a userspace visible breakage. As the changelog notes, this

Re: powerpc/4xx: Regression failed on sil24 (and other) drivers

2011-06-28 Thread Benjamin Herrenschmidt
On Mon, 2011-06-27 at 06:31 -0500, Ayman El-Khashab wrote: On Mon, Jun 27, 2011 at 08:19:56PM +1000, Benjamin Herrenschmidt wrote: On Sat, 2011-06-25 at 18:52 -0500, Ayman El-Khashab wrote: I noticed during a recent development with the 460SX that a simple device that once worked stopped.

Re: [PATCH 2/2] Add cpufreq driver for Momentum Maple boards

2011-06-28 Thread Benjamin Herrenschmidt
Before I comment on this last one, a quick Q. for Dave: Do you want to handle this or should I merge it via powerpc.git ? (It depends on another change to the arch code to expose the SCOM functions that it uses, and that patch is going to be in my -next branch). Now some remaining small nits: On

Re: [PATCH 1/2] mm: Move definition of MIN_MEMORY_BLOCK_SIZE to a header

2011-06-28 Thread Benjamin Herrenschmidt
On Tue, 2011-06-14 at 10:57 +1000, Benjamin Herrenschmidt wrote: The macro MIN_MEMORY_BLOCK_SIZE is currently defined twice in two .c files, and I need it in a third one to fix a powerpc bug, so let's first move it into a header Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org

Re: [PATCH 2/2] Add cpufreq driver for Momentum Maple boards

2011-06-28 Thread Dave Jones
On Wed, Jun 29, 2011 at 01:28:30PM +1000, Ben Herrenschmidt wrote: Before I comment on this last one, a quick Q. for Dave: Do you want to handle this or should I merge it via powerpc.git ? (It depends on another change to the arch code to expose the SCOM functions that it uses, and that

perf_event_open system call support in powerpc

2011-06-28 Thread ashwath narasimhan
Hello, I am new to the powerpc architecture and I am trying to use perf_event_open() system call for power pc architecture (e500mc) using 2.6.32 kernel distribution. Is this system call number supported for power pc architecture? If yes, is there something similar to

Re: [RFC][PATCH] Kexec support for PPC440x

2011-06-28 Thread Suzuki Poulose
On 06/03/11 19:23, Sebastian Andrzej Siewior wrote: Suzuki Poulose wrote: The way you setup the 1:1 mapping should be close to what you are doing on kernel entry.Isn't it possible to include the file here and in the entry code? I will make this change and resend the patch. I took a look at