Re: Support for multiple MSI interrupts on MPC8377

On Wed, 2011-11-02 at 16:02 -0500, Giffel, Brad wrote: > I’m working a project using a Spartan 6 FPGA with a PCIe interface and > MSI interrupts. I want to use multiple MSI interrupts (MSI-X is not > supported in the FPGA PCIe core) but the current Linux distribution > (3.0.8) prevents that (lines

[PATCH v3] asm-generic/gpio.h: merge basic gpiolib wrappers

Rather than requiring architectures that use gpiolib but don't have any need to define anything custom to copy an asm/gpio.h, merge this code into the asm-generic/gpio.h. We add ifdef checks so that arches can still override things while using the asm-generic/gpio.h, but on a more fine grained per

Re: What does rmo/tce stand for in powerpc?

2011/11/3 Scott Wood > On 11/02/2011 06:17 AM, Ryan Wang wrote: > > > > > > 2011/11/2 Nishanth Aravamudan mailto:n...@us.ibm.com>> > > > > Hi Ryan, > > > > On 01.11.2011 [14:25:43 +0800], Ryan Wang wrote: > > > Hi, > > > > > > In kernel source comments, I saw the words: > >

Re: Regression: patch " hvc_console: display printk messages on console." causing infinite loop with 3.2-rc0 + Xen.

On Wed, Nov 02, 2011 at 12:13:09PM +1100, Stephen Rothwell wrote: > Hi Greg, > > On Thu, 27 Oct 2011 07:48:06 +0200 Greg KH wrote: > > > > On Thu, Oct 27, 2011 at 01:30:08AM -0400, Konrad Rzeszutek Wilk wrote: > > > Hey Miche. > > > > > > The git commit 361162459f62dc0826b82c9690a741a940f457f0:

[PATCH 4/4] powerpc/time: Fix some style issues

Fix some formatting issues and use the DECREMENTER_MAX define instead of 0x7fff. Signed-off-by: Anton Blanchard --- Index: linux-build/arch/powerpc/kernel/time.c === --- linux-build.orig/arch/powerpc/kernel/time.c 2011-11-03 10:

[PATCH 3/4] powerpc/time: Remove unnecessary sanity check of decrementer expiration

The clockevents code uses max_delta_ns to avoid calling a clockevent with too large a value. Remove the redundant version of this in the timer_interrupt code. Signed-off-by: Anton Blanchard --- Index: linux-build/arch/powerpc/kernel/time.c ===

[PATCH 2/4] powerpc/time: Use clocksource_register_hz

Use clocksource_register_hz which calculates the shift/mult factors for us. Signed-off-by: Anton Blanchard --- Index: linux-build/arch/powerpc/kernel/time.c === --- linux-build.orig/arch/powerpc/kernel/time.c 2011-11-03 10:19:59.493

[PATCH 1/4] powerpc/time: Use clockevents_calc_mult_shift

We can use clockevents_calc_mult_shift instead of doing all the work ourselves. Signed-off-by: Anton Blanchard --- Index: linux-build/arch/powerpc/kernel/time.c === --- linux-build.orig/arch/powerpc/kernel/time.c 2011-11-03 10:19:55

[PATCH 0/4] PowerPC time fixes

Switch to using the common clockevents_calc_mult_shift and clocksource_register_hz functions, and do some cleanup along the way. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

[PATCH] powerpc: Add System RAM to /proc/iomem

We've resisted adding System RAM to /proc/iomem because it is the wrong place for it. Unfortunately we continue to find tools that rely on this behaviour so give up and add it in. Signed-off-by: Anton Blanchard --- Index: linux-build/arch/powerpc/mm/mem.c ===

Support for multiple MSI interrupts on MPC8377

I'm working a project using a Spartan 6 FPGA with a PCIe interface and MSI interrupts. I want to use multiple MSI interrupts (MSI-X is not supported in the FPGA PCIe core) but the current Linux distribution (3.0.8) prevents that (lines 23 to 25 in arch/powerpc/kernel/msi.c). What's the story h

Re: [PATCH v2 1/5] [ppc] Process dynamic relocations for kernel

On Tue, 2011-10-25 at 17:23 +0530, Suzuki K. Poulose wrote: > The following patch implements the dynamic relocation processing for > PPC32 kernel. relocate() accepts the target virtual address and relocates > the kernel image to the same. Hi Suzuki, Thanks for the patches. I've been testing th

fpga driver on custom PPC target platform (P4080) ...

Dear Tree lovers, I'm in the process of designing and implementing a Linux device driver for a Xilinx V6 FPGA which can be loaded from the CPU (P4080) on our target board (and optionally 2 additional FPGA's on a riser card). The programming pins of the FPGAs are tied to a MUX (PCA9539) on an i2c

[PATCH RFC 0/3] Support multiple VirtioConsoles.

This patchset applies to linux-next/next-2002. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues associated with trying to establish multiple virtio consoles. I'm trying to start a guest via KVM that supports multiple vi

Re: What does rmo/tce stand for in powerpc?

On 11/02/2011 06:17 AM, Ryan Wang wrote: > > > 2011/11/2 Nishanth Aravamudan mailto:n...@us.ibm.com>> > > Hi Ryan, > > On 01.11.2011 [14:25:43 +0800], Ryan Wang wrote: > > Hi, > > > > In kernel source comments, I saw the words: > > '' > > > > alloc_top is set to

Re: What does rmo/tce stand for in powerpc?

On 02.11.2011 [19:17:20 +0800], Ryan Wang wrote: > 2011/11/2 Nishanth Aravamudan > > > Hi Ryan, > > > > On 01.11.2011 [14:25:43 +0800], Ryan Wang wrote: > > > Hi, > > > > > > In kernel source comments, I saw the words: > > > '' > > > > > > alloc_top is set to the top of RMO, eventually shrink dow

Re: What does rmo/tce stand for in powerpc?

2011/11/2 Nishanth Aravamudan > Hi Ryan, > > On 01.11.2011 [14:25:43 +0800], Ryan Wang wrote: > > Hi, > > > > In kernel source comments, I saw the words: > > '' > > > > alloc_top is set to the top of RMO, eventually shrink down if the > >

RE: [PATCH] powerpc/usb: use ioremap instead of base plus offset to access regs

>-Original Message- >From: David Laight [mailto:david.lai...@aculab.com] >Sent: Wednesday, November 02, 2011 5:07 PM >To: Xie Shaohui-B21989; linuxppc-dev@lists.ozlabs.org >Cc: linux-...@vger.kernel.org >Subject: RE: [PATCH] powerpc/usb: use ioremap instead of base plus offset >to access re

RE: [PATCH] powerpc/usb: use ioremap instead of base plus offset to access regs

> #ifndef CONFIG_ARCH_MXC > if (pdata->have_sysif_regs) > - usb_sys_regs = (struct usb_sys_interface *) > - ((u32)dr_regs + USB_DR_SYS_OFFSET); > + usb_sys_regs = ioremap(res->start + USB_DR_SYS_OFFSET, > + siz

[PATCH] powerpc/usb: use ioremap instead of base plus offset to access regs

Below are codes for accessing usb sysif_regs in driver: usb_sys_regs = (struct usb_sys_interface *) ((u32)dr_regs + USB_DR_SYS_OFFSET); these codes work in 32-bit, but in 64-bit, accessing members of 'usb_sys_regs' will cause call trace like below: Unable to handle kernel