On Wed, 2008-07-23 at 13:35 -0500, Robert Jennings wrote:
From: Robert Jennings [EMAIL PROTECTED]
Enable the driver to function in a Cooperative Memory Overcommitment (CMO)
environment.
The following changes are made to enable the driver for CMO:
* DMA mapping errors will not result in
Hi
i want to fill dummy struct snd_dma_buffer in which i want to pass base
address of allocated BUFFER DESCRIPTOR(BD).
help me.
Regards,
Dinesh dua
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
* Benjamin Herrenschmidt | 2008-07-24 08:12:48 [+1000]:
On Mon, 2008-07-21 at 17:57 -0500, Nate Case wrote:
On Fri, 2008-07-18 at 14:10 +0200, Sebastian Siewior wrote:
Commit 35b5f6b1a aka [PHYLIB: Locking fixes for PHY I/O potentially
sleeping]
changed the phydev-lock from spinlock into
Tony Breeds wrote:
On Wed, Jul 23, 2008 at 10:36:42AM +0200, [EMAIL PROTECTED] wrote:
Hi Christian,
A few comments inlined ...
[...]
+
static inline int kvm_para_available(void)
{
- return 0;
+ struct device_node *dn;
+
+ dn = of_find_node_by_path(/hypervisor);
Tony Breeds wrote:
On Wed, Jul 23, 2008 at 10:36:44AM +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt [EMAIL PROTECTED]
Hi Christian,
This adds the guest portion of the hypercall infrastructure, basically an
illegal instruction with a defined layout.
See
Tony Breeds wrote:
On Wed, Jul 23, 2008 at 10:36:41AM +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt [EMAIL PROTECTED]
This patch series implements a paravirtualization interface using:
- the device tree mechanism to pass hypervisor informations to the guest
- hypercalls for
Currently, tarball builds for powerpc kernels don't have any boot
images (other than vmlinux) present.
Add support for powerpc builds in the buildtar script, to include
a few default images.
Signed-off-by: Jeremy Kerr [EMAIL PROTECTED]
---
RFC: any requests for more/less boot images?
---
The watchdog driver mpc8xx_wdt.c was a device interface to
arch/ppc/syslib/m8xx_wdt.c for MPC8xx hardware. Now that ARCH=ppc is
gone, this driver is of no more use. For ARCH=powerpc, MPC8xx hardware
is supported by mpc8xxx_wdt.c.
Signed-off-by: Jochen Friedrich [EMAIL PROTECTED]
---
From: Sebastien Dugue [EMAIL PROTECTED]
Date: Tue, 22 Jul 2008 13:05:24 +0200
Subject: [PATCH][RT] powerpc - XICS: move the call to irq_radix_revmap from
xics_startup to xics_host_map
This patch moves the insertion of an irq into the reverse mapping radix tree
from xics_startup() into
(This is resend as vger dropped my previous attempt, sorry for the duplication)
Hi,
here are 2 patches for fixing the following bug occuring on IBM pSeries under
an RT kernel:
BUG: sleeping function called from invalid context swapper(1) at
kernel/rtmutex.c:739
in_atomic():1 [0002],
From: Sebastien Dugue [EMAIL PROTECTED]
Date: Tue, 22 Jul 2008 11:56:41 +0200
Subject: [PATCH][RT] powerpc - Make the irq reverse mapping radix tree lockless
The radix tree used by interrupt controllers for their irq reverse mapping
(currently only the XICS found on pSeries) have a complex
On Thu, 24 Jul 2008 08:17:38 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
The root cause of this bug lies in the fact that the XICS interrupt
controller
uses a radix tree for its reverse irq mapping and that we cannot allocate
the tree
nodes (even GFP_ATOMIC) with
On Thursday 24 July 2008 20:50, Sebastien Dugue wrote:
From: Sebastien Dugue [EMAIL PROTECTED]
Date: Tue, 22 Jul 2008 11:56:41 +0200
Subject: [PATCH][RT] powerpc - Make the irq reverse mapping radix tree
lockless
The radix tree used by interrupt controllers for their irq reverse
mapping
This patch introduces baudrate setting support via the generic clock API.
When present the optional device tree clock property is used instead of
fsl-cpm-brg. Platforms can then define complex clock schemes, to output
the serial clock on an external pin for instance.
This is required to support
On Wed, Jul 23, 2008 at 11:34:28PM -0400, Jon Smirl wrote:
This lets me build again, no clue if it is the correct fix.
No, I don't think that this is correct. OF_GPIO isn't GENERIC_GPIO
provider. GPIO controllers should select GENERIC_GPIO instead.
Though, with this patch:
On Thu, 24 Jul 2008 21:11:34 +1000 Nick Piggin [EMAIL PROTECTED] wrote:
On Thursday 24 July 2008 20:50, Sebastien Dugue wrote:
From: Sebastien Dugue [EMAIL PROTECTED]
Date: Tue, 22 Jul 2008 11:56:41 +0200
Subject: [PATCH][RT] powerpc - Make the irq reverse mapping radix tree
lockless
Hi Anton,
Though, with this patch:
http://lkml.org/lkml/2008/7/10/269
We'll only have to select ARCH_WANT_OPTIONAL_GPIOLIB. Maybe for whole
powerpc.
That would simplify the GPIO support patches for CPM1/2, as well.
Thanks,
Jochen
___
When generating a break condition on a serial port, the CPM must be told
beforehand how long the break should be. Unfortunately, this information is
not available through the current serial break handling API. This patch works
around the problem by requesting a 32767 characters break followed by a
Hi Kumar,
On Friday 18 July 2008, Kumar Gala wrote:
On Jul 18, 2008, at 10:30 AM, Jochen Friedrich wrote:
On Jun 18, 2008, at 12:08 PM, Laurent Pinchart wrote:
+#if defined(CONFIG_CPM2) || defined(CONFIG_8xx_GPIO)
+
+struct cpm2_ioports {
+ u32 dir, par, sor, odr, dat;
+ u32
On Jul 24, 2008, at 9:46 AM, Laurent Pinchart wrote:
Hi Kumar,
On Friday 18 July 2008, Kumar Gala wrote:
On Jul 18, 2008, at 10:30 AM, Jochen Friedrich wrote:
On Jun 18, 2008, at 12:08 PM, Laurent Pinchart wrote:
+#if defined(CONFIG_CPM2) || defined(CONFIG_8xx_GPIO)
+
+struct cpm2_ioports
On Jul 24, 2008, at 9:21 AM, Laurent Pinchart wrote:
When generating a break condition on a serial port, the CPM must be
told
beforehand how long the break should be. Unfortunately, this
information is
not available through the current serial break handling API. This
patch works
around
On Thursday 24 July 2008, Kumar Gala wrote:
On Jul 24, 2008, at 9:21 AM, Laurent Pinchart wrote:
When generating a break condition on a serial port, the CPM must be
told beforehand how long the break should be. Unfortunately, this
information is not available through the current
The Marvell chip SRAM was disabled and some reserved bit set by mistake.
This bug was found thanks to Martyn Welch.
Signed-off-by: Remi Machet [EMAIL PROTECTED]
---
arch/powerpc/boot/cuboot-c2k.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
This patch implement GPIO LIB support for the CPM2 GPIOs. The code can also be
used for CPM1 GPIO port E, as both cores are compatible at the register level.
Based on earlier work by Jochen Friedrich.
Signed-off-by: Laurent Pinchart [EMAIL PROTECTED]
Cc: Jochen Friedrich [EMAIL PROTECTED]
---
This patch replaces the get_mctrl/set_mctrl stubs with modem control line
read/write access through the GPIO lib.
Available modem control lines are described in the device tree using GPIO
bindings. The driver expect a GPIO pin for each of the CTS, RTS, DCD, DSR,
DTR and RI signals. Unused control
В Thu, 24 Jul 2008 12:22:05 +0200
Jochen Friedrich [EMAIL PROTECTED] пишет:
The watchdog driver mpc8xx_wdt.c was a device interface to
arch/ppc/syslib/m8xx_wdt.c for MPC8xx hardware. Now that ARCH=ppc is
gone, this driver is of no more use. For ARCH=powerpc, MPC8xx hardware
is supported by
Hiya,
Grant Likely and Josh Boyer organised a Bird of Feather session on Device Trees
today at the Ottawa Linux Symposium, about a dozen folk there all told.
Was agreed that there was now enough non-PowerPC specific interest in Device
Trees to make a generic list a useful thing to have, so
On Thu, 24 Jul 2008 14:36:09 -0400
Hugh Blemings [EMAIL PROTECTED] wrote:
Hiya,
Grant Likely and Josh Boyer organised a Bird of Feather session on
Device Trees today at the Ottawa Linux Symposium, about a dozen folk
there all told.
Was agreed that there was now enough non-PowerPC
On Thu, Jul 24, 2008 at 2:57 PM, Sean MacLennan [EMAIL PROTECTED] wrote:
On Thu, 24 Jul 2008 14:36:09 -0400
Hugh Blemings [EMAIL PROTECTED] wrote:
Hiya,
Grant Likely and Josh Boyer organised a Bird of Feather session on
Device Trees today at the Ottawa Linux Symposium, about a dozen folk
Hi,
I have noticed that the DMA allocation for non-coherent PowerPC
architecture is using a hard coded virtual memory address for its memory
pool. This address is typically 0xFF10 (set by
CONFIG_CONSISTENT_START) and can conflict with early ioremap in systems
that enable HIGHMEM.
Is there
I'm seeing warnings from the lockdep code itself in recent kernels on
a Power6 blade (v2.6.26 and benh's -next branch).
Something to do with powerpc's lazy interrupt-disabling, perhaps?
A couple of stack traces below, the first is from benh's tree, the
second is from 2.6.26. The lockdep
Remi Machet wrote:
I have noticed that the DMA allocation for non-coherent PowerPC
architecture is using a hard coded virtual memory address for its memory
pool. This address is typically 0xFF10 (set by
CONFIG_CONSISTENT_START) and can conflict with early ioremap in systems
that enable
Nathan Lynch wrote:
A couple of stack traces below, the first is from benh's tree, the
second is from 2.6.26. The lockdep self-tests all pass at boot.
Sorry, should have pointed out the code that is warning more
specifically.
RTAS daemon started
RTAS: event: 295, Type: Dump Notification
On Thu, 2008-07-24 at 14:29 -0500, Scott Wood wrote:
Remi Machet wrote:
I have noticed that the DMA allocation for non-coherent PowerPC
architecture is using a hard coded virtual memory address for its memory
pool. This address is typically 0xFF10 (set by
CONFIG_CONSISTENT_START) and
[putting linuxppc-dev on Cc:, hope you don't mind]
On 24 jul 2008, at 08:32, Chuck Meade wrote:
I wanted to reply to your original message regarding this, but sadly
I
had
already deleted it. So I am sending directly to you.
This patch broke my link.
Sorry. I didn't test with anything
Anybody else seeing these? With Linus' latest I get three of these
warnings: .tmp_vmlinux1, .tmp_vmlinux2, and vmlinux.
Ah, that's useful information, I think I know what's going on
now. What was your binutils version?
Segher
___
Linuxppc-dev
On Thu, 2008-07-24 at 14:23 -0500, Nathan Lynch wrote:
I'm seeing warnings from the lockdep code itself in recent kernels on
a Power6 blade (v2.6.26 and benh's -next branch).
Something to do with powerpc's lazy interrupt-disabling, perhaps?
A couple of stack traces below, the first is from
On Thu, 2008-07-24 at 14:38 -0500, Nathan Lynch wrote:
Nathan Lynch wrote:
A couple of stack traces below, the first is from benh's tree, the
second is from 2.6.26. The lockdep self-tests all pass at boot.
Sorry, should have pointed out the code that is warning more
specifically.
Benjamin Herrenschmidt wrote:
On Thu, 2008-07-24 at 14:23 -0500, Nathan Lynch wrote:
I'm seeing warnings from the lockdep code itself in recent kernels on
a Power6 blade (v2.6.26 and benh's -next branch).
Something to do with powerpc's lazy interrupt-disabling, perhaps?
A couple of
On Friday 25 July 2008, Benjamin Herrenschmidt wrote:
Call Trace:
[cfffbb10] [cfffbbb0] 0xcfffbbb0 (unreliable)
[cfffbbb0] [c05d8824] ._spin_unlock_irq+0x40/0x68
[cfffbc40] [c0426708] .ipr_ioa_reset_done+0x218/0x2ac
Just tried to build the latest version from Linus' tree and I am getting
a link error.
building with the pseries_defconfig
...
LD drivers/built-in.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 6 section mismatch(es).
To see full details build your kernel with:
'make
The per-cpu cpu_sibling_maps get out of sync if CPUs are
onlined/offlined at runtime. I don't believe this can cause any
oopses, but it does cause incorrect information to be displayed by
/sys/devices/system/cpu/cpu*/topology/thread_siblings.
Rather doing one initialization pass over all CPUs at
On Fri, 25 Jul 2008 00:29:28 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
Anybody else seeing these? With Linus' latest I get three of these
warnings: .tmp_vmlinux1, .tmp_vmlinux2, and vmlinux.
Ah, that's useful information, I think I know what's going on
now. What was your binutils
Jon Tollefson wrote:
Just tried to build the latest version from Linus' tree and I am getting
a link error.
building with the pseries_defconfig
...
LD drivers/built-in.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 6 section mismatch(es).
To see full details
Segher Boessenkool wrote:
[putting linuxppc-dev on Cc:, hope you don't mind]
On 24 jul 2008, at 08:32, Chuck Meade wrote:
I wanted to reply to your original message regarding this, but sadly I
had
already deleted it. So I am sending directly to you.
This patch broke my link.
Sorry.
On Thu, 24 Jul 2008 19:17:33 -0400
Sean MacLennan [EMAIL PROTECTED] wrote:
On Fri, 25 Jul 2008 00:29:28 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
Anybody else seeing these? With Linus' latest I get three of these
warnings: .tmp_vmlinux1, .tmp_vmlinux2, and vmlinux.
Ah,
Just tried to build the latest version from Linus' tree and I am
getting
a link error.
I can reproduce this now, with 3.4.6 + 2.15, on powerpc64 defconfig
(with the drivers that don't compile with 3.4.6 disabled).
I have a fix for the warning with 2.17, but that's just a warning,
so I'll wait
I can help you by testing on 2.15. Send me alternate vmlinux.lds.S
files
to try, and I will test and get back to you ASAP.
No, I will not send you randomly changed source files and hope they
will do something useful for you. Instead, why not provide me the
information I asked for? What
My previous patch to fix compilation with binutils-2.17 causes
a file truncated build error from ld with binutils 2.15 (and
possibly older), and a warning with 2.16 and 2.17.
This fixes it.
Signed-off-by: Segher Boessenkool [EMAIL PROTECTED]
---
arch/powerpc/kernel/vmlinux.lds.S |2 +-
1
Hi all,
Today's linux-next (really just Linus' tree) build (powerpc
ppc64_defconfig) failed like this:
fs/nfs/nfsroot.c:130: error: tokens causes a section type conflict
tokens is a match_table_t which has const added to it in commit
f9247273cb69ba101877e946d2d83044409cc8c5 UFS: add const to
Segher Boessenkool wrote:
My previous patch to fix compilation with binutils-2.17 causes
a file truncated build error from ld with binutils 2.15 (and
possibly older), and a warning with 2.16 and 2.17.
This fixes it.
Signed-off-by: Segher Boessenkool [EMAIL PROTECTED]
Hi Segher,
That
On Thu, Jul 24, 2008 at 10:17:31AM +0200, Christian Ehrhardt wrote:
The aim is not really fixed. It would be nice to get into 2.6.27, but
since I can't yet expect how long it takes ...
Ahh okay, Id say given that we're 2/3rds through the merge window then
2.8.28 is a safer target.
Actually
Currently, tarball builds for powerpc kernels don't have any boot
images (other than vmlinux) present.
Add support for powerpc builds in the buildtar script, to include
a few default images.
Signed-off-by: Jeremy Kerr jk at ozlabs.org
---
RFC: any requests for more/less boot images?
On Fri, 25 Jul 2008 02:08:41 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
My previous patch to fix compilation with binutils-2.17 causes
a file truncated build error from ld with binutils 2.15 (and
possibly older), and a warning with 2.16 and 2.17.
This fixes it.
And it does ;)
Segher Boessenkool wrote:
My previous patch to fix compilation with binutils-2.17 causes
a file truncated build error from ld with binutils 2.15 (and
possibly older), and a warning with 2.16 and 2.17.
This fixes it.
Signed-off-by: Segher Boessenkool [EMAIL PROTECTED]
---
Milton,
Yes. How about all dtbImage, zImage, cuboot, treeboot, etc
that are newer than vmlinux?
The existing arch code doesn't do any checks for timestamps, perhaps
this would be better implemented as an arch-independent change?
(but would you like me to add treeboot and cuboot?)
Cheers,
On Wed, 2008-07-23 at 13:10 -0300, Luis Machado wrote:
On Wed, 2008-07-23 at 11:53 -0400, Josh Boyer wrote:
Shouldn't this (and other places) be:
#if defined(CONFIG_44x) || defined(CONFIG_BOOKE)
if you are going to exclude 40x for now? Otherwise this is still
enabled on 405 and
Hi Sam,
On Mon, 7 Jul 2008 18:40:38 +1000 Stephen Rothwell [EMAIL PROTECTED] wrote:
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
arch/powerpc/platforms/cell/spu_base.c: In function '__spu_trap_data_seg':
arch/powerpc/platforms/cell/spu_base.c:194: error: duplicate
Concurrency between readers and writers are handled by the intrinsic
properties of the concurrent radix tree. Concurrency between the tree
initialization which is done asynchronously with readers and writers access
is handled via an atomic variable (revmap_trees_allocated) set when the
59 matches
Mail list logo
