On Fri, 2009-04-03 at 14:08 +0200, Geert Uytterhoeven wrote:
> Hi Ben, Kumar,
>
> Finally (after ca. 1.5 years), he're an updated version of my patch to keep
> track of emulated instructions. In the light of Kumar's `Emulate enough of
> SPE
> instructions to make gcc happy' patch, he proba
The interrupt controller was not handling level interrupts correctly
such that duplicate interrupts were happening. This fixes the problem
and adds edge type interrupts which are needed in Xilinx hardware.
Signed-off-by: John Linn
---
arch/powerpc/sysdev/xilinx_intc.c | 112
Previously, if udbg was using the CPM uart, and the normal CPM uart driver
was enabled, but the console was directed elsewhere, udbg would not be
stopped prior to initialization. This resulted in udbg hanging forever
waiting for the CPM to process a descriptor.
Signed-off-by: Scott Wood
---
dri
Add aliases, and correct CS0 offset to match how u-boot
programs it (this was not a problem with cuImage because
the wrapper would reprogram the localbus to match the device
tree).
Signed-off-by: Scott Wood
---
arch/powerpc/boot/dts/pq2fads.dts | 20 ++--
1 files changed, 14 in
Previously, this caused NULL to sometimes be passed as a device
to the DMA code. With recent DMA changes, that now causes a BUG().
Signed-off-by: Scott Wood
---
This is a regression triggered by DMA changes; please apply for 2.6.30.
drivers/serial/cpm_uart/cpm_uart_core.c |6 +++---
1 file
I unfortunately don't have an answer for you, but I have had problems
in the past with GDB on virtex ppc405. I don't know if it is related.
I'll try to dig up my old notes, but no promises.
g.
On Wed, Mar 4, 2009 at 11:36 AM, Frederic LEGER
wrote:
> Hi,
>
> At the moment I can't set any breakp
On Wed, Apr 1, 2009 at 1:16 PM, Roderick Colenbrander
wrote:
> Hi,
>
> As requested by Grant Likely here the same patch but now inlined.
word wrapped. neener neener.
Mostly looks good to me. It would help to split the PCI driver out
into a separate patch from the board support. Comments below
On Fri, Apr 03 2009, Geert Uytterhoeven wrote:
> Remove the mutex serializing access to the cache.
> Instead, queue up new requests on a list if the driver is busy.
>
> This improves sequential write performance by ca. 2%.
Great, precisely the method I wanted to see there! I've added your three
p
Hi:
Did you try the early kernel printk option in kernel hacking. It can
give some
very helpful information. Make sure the address for the physical uart
address is
passed in correctly.
Feng
Tirumala Reddy Marri wrote:
I am not sure if I understand correctly. But Looks like you are not
pass
I am not sure if I understand correctly. But Looks like you are not
passing the device tree along with kernel image and RAMDISK(you may not
need it if you are using NFS mount). You boot command should some what
look like this "bootm kernel_addr ramdisk_addr devtree_addr" or "bootm
kernel_addr - de
> It's because the irqs are remapped by the kernel, the number in the
> device tree is a hardware irq number. The number you're printing out is
> a virtual irq number.
> of_irq_to_resource() is doing the remapping for you.
> You can turn on CONFIG_VIRQ_DEBUG and you'll get a file in debugfs that
Josh Boyer writes:
> [...] While I would love to believe that systemtap should work
> everywhere, I can't really see it running on an embedded board at
> this point.
FWIW, we have had people running (not compiling) systemtap probe
modules on embedded systems. See "stap -p4" or "stap-server".
Commit 4ae0ff6 "powerpc: expect all devices calling dma
ops to have archdata set" assumes that all devices use
correct dma ops. However FEC uses dma ops from 'eth'
device which doesn't have proper archdata. This patch
makes FEC use dma operation from OF 'ethernet' device,
similarly to what other dr
This is already fixed in the netdev tree
g.
On Fri, Apr 3, 2009 at 8:16 AM, Grzegorz Bernacki wrote:
> Commit 4ae0ff6 "powerpc: expect all devices calling dma
> ops to have archdata set" assumes that all devices use
> correct dma ops. However FEC uses dma ops from 'eth'
> device which doesn't ha
On Apr 3, 2009, at 7:08 AM, Geert Uytterhoeven wrote:
Hi Ben, Kumar,
Finally (after ca. 1.5 years), he're an updated version of my patch
to keep
track of emulated instructions. In the light of Kumar's `Emulate
enough of SPE
instructions to make gcc happy' patch, he probably also w
On Fri, Apr 3, 2009 at 3:55 AM, Stefan Roese wrote:
> This patch adds support to handle multiple non-identical chips in one
> flash device tree node. It also adds concat support to physmap_of. This
> makes it possible to support e.g. the Intel P30 48F4400 chips which
> internally consists of 2 non
Remove the mutex serializing access to the cache.
Instead, queue up new requests on a list if the driver is busy.
This improves sequential write performance by ca. 2%.
Signed-off-by: Geert Uytterhoeven
---
drivers/block/ps3vram.c | 55 ++
1 files ch
From: Jim Paris
From: Jim Paris
Signed-off-by: Geert Uytterhoeven
---
drivers/block/ps3vram.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/ps3vram.c b/drivers/block/ps3vram.c
index 6e73868..3c9ad19 100644
--- a/drivers/block/ps3vram.c
+++ b/drivers
Use proc_create_data() to avoid race conditions.
Reported-by: Alexey Dobriyan
Signed-off-by: Geert Uytterhoeven
---
drivers/block/ps3vram.c |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/block/ps3vram.c b/drivers/block/ps3vram.c
index 2e79d2c..6e73868 10
Signed-off-by: Geert Uytterhoeven
---
drivers/block/ps3vram.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/block/ps3vram.c b/drivers/block/ps3vram.c
index 8eddef3..2e79d2c 100644
--- a/drivers/block/ps3vram.c
+++ b/drivers/block/ps3vram.c
@@ -585,6 +585,7 @@ st
Hi Ben, Kumar,
Finally (after ca. 1.5 years), he're an updated version of my patch to keep
track of emulated instructions. In the light of Kumar's `Emulate enough of SPE
instructions to make gcc happy' patch, he probably also wants to keep track of
the actual runtime overhead.
Changes si
Benjamin Herrenschmidt wrote:
> > Thanks.
> >
Firstly sorry for the delay response.
> > Now, is there any reason you can't fold the fix inside the existing
> > fixup_device_tree_maple() fixup ? IE. Does it apply to any Maple board
> > or only this ATCA6101 ?
> >
I really don't validate this o
In the DTB tree created by firmware on some Maple 64bit targets, such as
ATCA6101,
these two properties, address&size, should be 2. But the actual corresponding
values
of host bridge node are set 1 incorrectly by the firmware, we have to provide
one
fixup function to fix that.
Signed-off-by:
Testing 2.6.29-git9 on Pegasos2 Chrp machine equipped with Marvell Discovery II
i was unable to see MV643xx gigabit nic option.
32-bit platforms that relied on PPC32 && PPC_MULTIPLATFORM now rely
on 6xx then this one must be updated too.
-N
---
drivers/net/{Kconfig.orig => Kconfig} |2 +-
On Fri, 2009-04-03 at 16:51 +0900, yamazaki seiji wrote:
> I set the Interrupt ID number 17.
> But kernel gives the Interrupt ID number 19.
>
> I wont to know the reasen.
> Please tell me.
It's because the irqs are remapped by the kernel, the number in the
device tree is a hardware irq number. Th
Commit-ID: a095bdbb136f7bed96b7adf5aa1dd27bb2f839bf
Gitweb: http://git.kernel.org/tip/a095bdbb136f7bed96b7adf5aa1dd27bb2f839bf
Author: Stephen Rothwell
AuthorDate: Fri, 27 Mar 2009 23:08:34 +1100
Committer: Ingo Molnar
CommitDate: Thu, 2 Apr 2009 00:50:24 +0200
tracing, powerpc: fix po
Michael Ellerman 写道:
> On Fri, 2009-04-03 at 14:10 +0800, Harry Ciao wrote:
>
>> Setup a platform device for the CPC925 Memory Controller during system
>> booting up, against which CPC925 MC EDAC driver would be matched.
>>
>> Signed-off-by: Harry Ciao
>> ---
>> arch/powerpc/platforms/maple/se
This patch adds support to handle multiple non-identical chips in one
flash device tree node. It also adds concat support to physmap_of. This
makes it possible to support e.g. the Intel P30 48F4400 chips which
internally consists of 2 non-identical NOR chips on one die. Additionally
partitions now
Hi all,
I am running the Linux kernel 2.6.28.7 on my PPC8347 BRD.
I have another problem.
I use many external Interrupts.
one of them ,I setup
local...@f000 { //WDT,SW etc.k
reg = <0xf000 0x20>;
pci_i...@2{
interrupt-pa
Arnd Bergmann 写道:
On Thursday 02 April 2009, Harry Ciao wrote:
+#ifdef CONFIG_EDAC
+#define CPC925_MC_START0xf800
+#define CPC925_MC_END 0xf8ff /* sizeof 16MB */
+/* Register a platform device for CPC925 memory controller */
+static int __init maple_cpc925_eda
30 matches
Mail list logo