HFI creates interrupts each time a window is setup. This results in
a lot of messages in the kernel log buffer:
irq: irq 199007 on host null mapped to virtual irq 351
This box has over 3500 of them, causing more important kernel
messages to be overwritten. We can get at this information via
What is Xad. ? (btw, coding style FAIL !)
That's the struct I use to access the control registers of the hardware.
About the coding style, don't worry it's never going to make it into mainstream
as there's only one piece of that
hardware ever built ! (which is also why I didn't respect things
When enable CONFIG_PREEMPT we will trigger the following call trace:
BUG: scheduling while atomic: swapper/1/0x1000
...
krpobe always goes through the following path:
program_check_exception()
|
+ notify_die(DIE_BPT, breakpoint,...)
|
+
When kprobe these operations such as store-and-update-word for SP(r1),
stwu r1, -A(r1)
The program exception is triggered, and PPC always allocate an exception frame
as shown as the follows:
old r1 --
...
nip
gpr[2] ~ gpr[31]
gpr[1] - old r1
The following changes since commit af9719c3062dfe216a0c3de3fa52be6d22b4456c:
powerpc: Use -mtraceback=no (2011-07-01 13:49:27 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git next
Becky Bruce (1):
powerpc: Create
Hi,
I'd like to use a SRAM device (512K*8) connected to a MPC8377 localbus.
What's a decent way to do this (mmap'ed access) running v2.6.34 ?
Is platform RAM (drivers/mtd/maps/plat-ram.c) a good starting point ?
Any hints are welcome.
--
Regards,
Andre
MATRIX VISION GmbH, Talstrasse 16,
-Original Message-
From:
linuxppc-dev-bounces+tiejun.chen=windriver@lists.ozlabs.or
g
[mailto:linuxppc-dev-bounces+tiejun.chen=windriver.com@lists.o
zlabs.org] On Behalf Of Tiejun Chen
Sent: Friday, July 08, 2011 6:05 PM
To: b...@kernel.crashing.org; linuxppc-...@ozlabs.org
With KVM on Freescale booke parts we have currently two general types of
virtual platforms-- 1) an 85xx-like platform with e500v2 cpus,
etc, and 2) a P4080-like platform with a corenet based bus.
Today QEMU passes through to the guest a device tree with
a top level compatible of either MPC8544DS,
There is one place in the MPIC driver that assumes that the cores are numbered
from 0 to n-1. However, this is not true if the CPUs are not numbered
sequentially. This can happen on a eight-core SOC where cores two and three
are removed in the device tree. So instead of blindly looping, we
On Thu, May 19, 2011 at 08:34:52AM -, Timur Tabi wrote:
The ePAPR embedded hypervisor specification provides an API for byte
channels, which are serial-like virtual devices for sending and receiving
streams of bytes. This driver provides Linux kernel support for byte
channels via three
Greg KH wrote:
3) A tty driver, which is used to handle user-space input and output. The
byte channel used for the console is designated as the default tty.
Signed-off-by: Timur Tabi ti...@freescale.com
Doesn't apply at all to the tty-next tree, so I can't apply it here :(
I shall take
Greg KH wrote:
Doesn't apply at all to the tty-next tree, so I can't apply it here :(
Um, where exactly is the tty-next tree? The only thing I see that looks like it
is this:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6.git
But the description of this tree says, junk tree,
On Fri, Jul 08, 2011 at 05:15:47PM -0500, Timur Tabi wrote:
Greg KH wrote:
Doesn't apply at all to the tty-next tree, so I can't apply it here :(
Um, where exactly is the tty-next tree? The only thing I see that looks like
it
is this:
The ePAPR embedded hypervisor specification provides an API for byte
channels, which are serial-like virtual devices for sending and receiving
streams of bytes. This driver provides Linux kernel support for byte
channels via three distinct interfaces:
1) An early-console (udbg) driver. This
On Fri, Jul 8, 2011 at 1:43 PM, Yoder Stuart-B08248
b08...@freescale.com wrote:
MPC85xxDS - for a virtual machine for the e500v2 type platforms
and would support 85xx targets, plus P2020, P1022,etc
corenet-32-ds - for a virtual machine similar to the 32-bit P4080
Posting to correct list email...
Original Message
Subject: [PATCH] powerpc: convert to generic pci_*_flags
Date: Fri, 8 Jul 2011 21:21:24 -0500
From: Rob Herring robherri...@gmail.com
To: linuxppc-...@lists.infradead.org
CC: Rob Herring rob.herr...@calxeda.com, Benjamin
On Friday, July 8, 2011, Tabi Timur-B04825 b04...@freescale.com wrote:
On Fri, Jul 8, 2011 at 1:43 PM, Yoder Stuart-B08248
b08...@freescale.com wrote:
MPC85xxDS - for a virtual machine for the e500v2 type platforms
and would support 85xx targets, plus P2020, P1022,etc
17 matches
Mail list logo
