Hi Ira,
On Tue, Feb 08, 2011 at 03:37:46PM -0800, Ira W. Snyder wrote:
This driver allows userspace to access the data processing FPGAs on the
OVRO CARMA board. It has two modes of operation:
Thank you for making the changes, some more comments below.
+
+#define inode_to_dev(inode)
On Mon, 2011-02-07 at 14:54 +0100, Peter Zijlstra wrote:
On Mon, 2011-02-07 at 10:26 +1100, Benjamin Herrenschmidt wrote:
You missed:
diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
index 9813605..467d122 100644
--- a/arch/powerpc/kernel/smp.c
+++
On Wed, 2011-02-09 at 17:14 +1100, Benjamin Herrenschmidt wrote:
On Mon, 2011-02-07 at 14:54 +0100, Peter Zijlstra wrote:
On Mon, 2011-02-07 at 10:26 +1100, Benjamin Herrenschmidt wrote:
You missed:
diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
index
What I'm trying to achieve is to have an interrupt service routine
called for every rising edge on pin E2 of the MPC5200B.
The only CPU register setup (AFAIK) to let the CPU generate this
interrupt is to use the GPT (general purpose timer) function pin E2 is
attached to.
This function is
This driver allows userspace to access the data processing
FPGAs on the OVRO CARMA board. It has two modes of operation:
1) random access
This allows users to poke any DATA-FPGA registers by using mmap to map
the address region directly into their memory map.
I needed something
On Wed, Feb 09, 2011 at 04:30:23PM -, David Laight wrote:
This driver allows userspace to access the data processing
FPGAs on the OVRO CARMA board. It has two modes of operation:
1) random access
This allows users to poke any DATA-FPGA registers by using mmap to map
the
On Wed, Feb 09, 2011 at 12:33:25AM -0800, Dmitry Torokhov wrote:
Hi Ira,
On Tue, Feb 08, 2011 at 03:37:46PM -0800, Ira W. Snyder wrote:
This driver allows userspace to access the data processing FPGAs on the
OVRO CARMA board. It has two modes of operation:
Thank you for making the
On Wed, Feb 09, 2011 at 09:35:32AM -0800, Ira W. Snyder wrote:
On Wed, Feb 09, 2011 at 12:33:25AM -0800, Dmitry Torokhov wrote:
+
+ /* Warn if we are running in a degraded state, but do not fail */
+ if (priv-num_buffers MAX_DATA_BUFS) {
+ dev_warn(priv-dev, Unable to
On Mon, 2011-02-07 at 15:57 +1100, Benjamin Herrenschmidt wrote:
On Sat, 2010-11-13 at 20:15 -0800, Jim Keniston wrote:
Adapt the functions used to create and write to the RTAS-log partition
to work with any OS-type partition.
Signed-off-by: Jim Keniston jkeni...@us.ibm.com
---
On Mon, 2011-02-07 at 16:01 +1100, Benjamin Herrenschmidt wrote:
On Sat, 2010-11-13 at 20:15 -0800, Jim Keniston wrote:
Create the ibm,oops-log NVRAM partition, and capture the end of the printk
buffer in it when there's an oops or panic. If we can't create the
ibm,oops-log partition,
On Wed, 2011-02-02 at 01:45 -0600, Kumar Gala wrote:
On Feb 1, 2011, at 12:48 PM, Dave Kleikamp wrote:
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh Boyer jwbo...@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
On Wed, 2011-02-02 at 13:43 +1100, David Gibson wrote:
On Tue, Feb 01, 2011 at 12:48:46PM -0600, Dave Kleikamp wrote:
These are completely independent OS instances, each running on 2
cores.
[snip]
+/memreserve/ 0x01f0 0x0010;
A comment describing what this reserved section is
These patches add Asynchonous MultiProcessing support for the 47x chipset.
This allows independent OS instances to run on separate cores.
v3:
1. switched from using compatible string to boolean cooperative-partition
2. fixed missing type in boot wrapper
3. fixed check for unspecified memory
Since other OS's may be running on the other cores don't use tlbivax
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh Boyer jwbo...@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
---
arch/powerpc/include/asm/mmu.h |2 +-
These are completely independent OS instances, each running on 2 cores.
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh Boyer jwbo...@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
---
arch/powerpc/boot/Makefile
so that it can use information from the device tree.
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh Boyer jwbo...@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
---
arch/powerpc/kernel/setup_32.c |6 +++---
1 files
The 44x code (which is shared by 47x) assumes the available physical memory
begins at 0x. This is not necessarily the case in an AMP
environment.
Support CONFIG_RELOCATABLE for 476 in order to allow the kernel to be
loaded into a higher memory range.
Signed-off-by: Dave Kleikamp
For AMP, different kernel instances load into separate memory regions.
Read the start of memory from the device tree and limit the memory to what's
specified in the device tree.
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh
Allow the early debug uart address to be overridden from the kernel
command line.
I would have preferred use the uart's virtual-reg property, but the device
tree hasn't been unflatted yet, and I don't know a reliable way to find it.
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc:
On Wed, Feb 09, 2011 at 10:27:40AM -0800, Dmitry Torokhov wrote:
[ snip stuff I've already fixed in the next version ]
The requirement is that the device stay open during reconfiguration.
This provides for that. Readers just block for as long as the device is
not producing data.
OK,
On Wed, Feb 09, 2011 at 03:35:45PM -0800, Ira W. Snyder wrote:
On Wed, Feb 09, 2011 at 10:27:40AM -0800, Dmitry Torokhov wrote:
[ snip stuff I've already fixed in the next version ]
The requirement is that the device stay open during reconfiguration.
This provides for that. Readers
On Wed, Feb 09, 2011 at 03:42:31PM -0800, Dmitry Torokhov wrote:
On Wed, Feb 09, 2011 at 03:35:45PM -0800, Ira W. Snyder wrote:
On Wed, Feb 09, 2011 at 10:27:40AM -0800, Dmitry Torokhov wrote:
[ snip stuff I've already fixed in the next version ]
The requirement is that the
Hello everyone,
This is the sixth posting of these drivers, taking into account comments from
earlier postings. I would appreciate as much review as you can offer.
RFCv5 - RFCv6:
- change locking in several functions
- use list_move_tail() to simplify code
- remove unused helper functions
RFCv4
This driver allows userspace to access the data processing FPGAs on the
OVRO CARMA board. It has two modes of operation:
1) random access
This allows users to poke any DATA-FPGA registers by using mmap to map
the address region directly into their memory map.
2) correlation dumping
When
This adds support for programming the data processing FPGAs on the OVRO
CARMA board. These FPGAs have a special programming sequence that
requires that we program the Freescale DMA engine, which is only
available inside the kernel.
Signed-off-by: Ira W. Snyder i...@ovro.caltech.edu
---
On Wed, Feb 09, 2011 at 04:10:55PM -0800, Ira W. Snyder wrote:
On Wed, Feb 09, 2011 at 03:42:31PM -0800, Dmitry Torokhov wrote:
On Wed, Feb 09, 2011 at 03:35:45PM -0800, Ira W. Snyder wrote:
On Wed, Feb 09, 2011 at 10:27:40AM -0800, Dmitry Torokhov wrote:
[ snip stuff I've already
26 matches
Mail list logo
