Re: [PATCH v2] Make 83xx perfmon support selectable

2008-03-08 Thread Jerry Van Baren
Andy Fleming wrote:
> Not all e300 cores support the performance monitors, and the ones
> that don't will be confused by the mf/mtpmr instructions.  This
> allows the support to be optional, so the 8349 can turn it off
> while the 8379 can turn it on.  Sadly, those aren't config options,
> so it will be left to the defconfigs and the users to make that
> determination.
> 
> Signed-off-by: Andy Fleming <[EMAIL PROTECTED]>

Thanks, Andy!

FWIIW,
Acked-by: Gerald Van Baren <[EMAIL PROTECTED]>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH] [POWERPC] bootwrapper: Allow specifying of image physical offset

2008-03-08 Thread Kumar Gala

On Mar 7, 2008, at 7:44 PM, Geoff Levand wrote:

> On 03/07/2008 08:55 AM, Kumar Gala wrote:
>> Normally we assume kernel images will be loaded at offset 0. However
>> there are situations, like when the kernel itself is running at a  
>> non-zero
>> physical address, that we don't want to load it at 0.
>>
>> Allow the wrapper to take an offset.  We use this when building u- 
>> boot images.
>>
>> Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
>> ---
>> arch/powerpc/boot/Makefile |7 +++
>> arch/powerpc/boot/wrapper  |   12 ++--
>> 2 files changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
>> index f43dd6e..1b4bfc6 100644
>> --- a/arch/powerpc/boot/Makefile
>> +++ b/arch/powerpc/boot/Makefile
>> @@ -35,6 +35,12 @@ endif
>>
>> BOOTCFLAGS   += -I$(obj) -I$(srctree)/$(obj) -I$(srctree)/$(src)/libfdt
>>
>> +ifdef CONFIG_MEMORY_START
>> +MEMBASE=$(CONFIG_MEMORY_START)
>
> We have the powerpc config option CONFIG_KERNEL_START.  I'm
> wondering  how this CONFIG_MEMORY_START is different.  I just
> did a quick search, and it seems that CONFIG_MEMORY_START is
> only defined for the renesas arch's.

KERNEL_START is the virtual address of the kernel.  It makes no claims  
about what the physical address is.

MEMORY_START will be the physical address that the kernel is at.  This  
will only be supported on platforms like Book-e that can have  
exception vectors at roughly any address.

- k
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


[PATCH] sbc8548: fix incorrect PCI-X and PCI interrupt map

2008-03-08 Thread Jeremy McNicoll
The following patch allows interrupts to occur on the
sbc8548. Currently PCI and PCI-X devices get assigned an IRQ
but the interrupt count never increases.  This solves the
problem and adds PCI support as well.

Signed-off-by: Jeremy McNicoll <[EMAIL PROTECTED]>
Signed-off-by: Paul Gortmaker <[EMAIL PROTECTED]>
---
 arch/powerpc/boot/dts/sbc8548.dts |   16 +++-
 1 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/arch/powerpc/boot/dts/sbc8548.dts 
b/arch/powerpc/boot/dts/sbc8548.dts
index 14be38a..b86e65d 100644
--- a/arch/powerpc/boot/dts/sbc8548.dts
+++ b/arch/powerpc/boot/dts/sbc8548.dts
@@ -184,11 +184,17 @@
cell-index = <0>;
interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
interrupt-map = <
-   /* IDSEL 0x01 (PCI-X slot) */
-   0x0800 0x0 0x0 0x1 &mpic 0x0 0x1
-   0x0800 0x0 0x0 0x2 &mpic 0x1 0x1
-   0x0800 0x0 0x0 0x3 &mpic 0x2 0x1
-   0x0800 0x0 0x0 0x4 &mpic 0x3 0x1>;
+   /* IDSEL 0x01 (PCI-X slot) @66MHz */
+   0x0800 0x0 0x0 0x1 &mpic 0x2 0x1
+   0x0800 0x0 0x0 0x2 &mpic 0x3 0x1
+   0x0800 0x0 0x0 0x3 &mpic 0x4 0x1
+   0x0800 0x0 0x0 0x4 &mpic 0x1 0x1
+
+   /* IDSEL 0x11 (PCI, 3.3V 32bit) @33MHz */
+   0x8800 0x0 0x0 0x1 &mpic 0x2 0x1
+   0x8800 0x0 0x0 0x2 &mpic 0x3 0x1
+   0x8800 0x0 0x0 0x3 &mpic 0x4 0x1
+   0x8800 0x0 0x0 0x4 &mpic 0x1 0x1>;
 
interrupt-parent = <&mpic>;
interrupts = <0x18 0x2>;
-- 
1.5.3.7

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


[PATCH] Export pmu_* variables unconditionally

2008-03-08 Thread Guido Günther
Hi,
This is a resend, since it's still unfixed in current Linus git and I
didn't see any comments (please cc: me since I'm not subscribed):

Otherwise without CONFIG_SUSPEND we have:

ERROR: "pmu_batteries" [drivers/macintosh/apm_emu.ko] undefined!
ERROR: "pmu_battery_count" [drivers/macintosh/apm_emu.ko] undefined!
ERROR: "pmu_power_flags" [drivers/macintosh/apm_emu.ko] undefined!

on PPC32. The variables aren't wrapped in '#if defined(CONFIG_SUSPEND)'
so we probably shouldn't wrap the exports either. Fixes compilation on
ppc32.

Signed-off-by: Guido Guenther <[EMAIL PROTECTED]>
---
 drivers/macintosh/via-pmu.c |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/macintosh/via-pmu.c b/drivers/macintosh/via-pmu.c
index 296edcb..399fc7f 100644
--- a/drivers/macintosh/via-pmu.c
+++ b/drivers/macintosh/via-pmu.c
@@ -2528,7 +2528,7 @@ EXPORT_SYMBOL(pmu_wait_complete);
 EXPORT_SYMBOL(pmu_suspend);
 EXPORT_SYMBOL(pmu_resume);
 EXPORT_SYMBOL(pmu_unlock);
-#if defined(CONFIG_SUSPEND) && defined(CONFIG_PPC32)
+#if defined(CONFIG_PPC32)
 EXPORT_SYMBOL(pmu_enable_irled);
 EXPORT_SYMBOL(pmu_battery_count);
 EXPORT_SYMBOL(pmu_batteries);
-- 
1.5.4.2

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


[PATCH] Always define pmu_sys_suspended

2008-03-08 Thread Guido Günther
Hi,
This is a resend, since it's still unfixed in current Linus git and I
didn't see any comments (please cc: me since I'm not subscribed):

In current Linus git pmu_sys_suspended is only defined if
CONFIG_SUSPEND is set, so compilation fails with:

drivers/built-in.o: In function `pmu_led_set':
via-pmu-led.c:(.text+0x48622): undefined reference to `pmu_sys_suspended'
via-pmu-led.c:(.text+0x48626): undefined reference to `pmu_sys_suspended'
drivers/built-in.o: In function `pmu_req_done':
via-pmu-led.c:(.text+0x48696): undefined reference to `pmu_sys_suspended'
via-pmu-led.c:(.text+0x4869a): undefined reference to `pmu_sys_suspended'
make: *** [.tmp_vmlinux1] Error 1

since via-pmu-led.c uses it unconditionally. Instead of adding more '#ifdef'
clutter I moved it out of the #ifdef so it's always available. Need to fix
compilation on PPC32 without CONFIG_SUSPEND.

Signed-off-by: Guido Guenther <[EMAIL PROTECTED]>
---
 drivers/macintosh/via-pmu.c |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/macintosh/via-pmu.c b/drivers/macintosh/via-pmu.c
index ebec663..296edcb 100644
--- a/drivers/macintosh/via-pmu.c
+++ b/drivers/macintosh/via-pmu.c
@@ -2437,8 +2437,8 @@ void pmu_blink(int n)
 }
 #endif /* DEBUG_SLEEP */
 
-#if defined(CONFIG_SUSPEND) && defined(CONFIG_PPC32)
 int pmu_sys_suspended;
+#if defined(CONFIG_SUSPEND) && defined(CONFIG_PPC32)
 
 static int pmu_sys_suspend(struct sys_device *sysdev, pm_message_t state)
 {
-- 
1.5.4.2

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev