[PATCH][for 2.6.28] Remove -mno-spe flags as they dont belong

2008-11-15 Thread Kumar Gala
For some unknown reason at Steven Rostedt added in disabling of the SPE
instruction generation for e500 based PPC cores in commit
6ec562328fda585be2d7f472cfac99d3b44d362a.

We are removing it because:

1. It generates e500 kernels that don't work
2. its not the correct set of flags to do this
3. we handle this in the arch/powerpc/Makefile already
4. its unknown in talking to Steven why he did this

Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
 kernel/Makefile |4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/kernel/Makefile b/kernel/Makefile
index 9a3ec66..19fad00 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -11,8 +11,6 @@ obj-y = sched.o fork.o exec_domain.o panic.o printk.o \
hrtimer.o rwsem.o nsproxy.o srcu.o semaphore.o \
notifier.o ksysfs.o pm_qos_params.o sched_clock.o
 
-CFLAGS_REMOVE_sched.o = -mno-spe
-
 ifdef CONFIG_FUNCTION_TRACER
 # Do not trace debug files and internal ftrace files
 CFLAGS_REMOVE_lockdep.o = -pg
@@ -21,7 +19,7 @@ CFLAGS_REMOVE_mutex-debug.o = -pg
 CFLAGS_REMOVE_rtmutex-debug.o = -pg
 CFLAGS_REMOVE_cgroup-debug.o = -pg
 CFLAGS_REMOVE_sched_clock.o = -pg
-CFLAGS_REMOVE_sched.o = -mno-spe -pg
+CFLAGS_REMOVE_sched.o = -pg
 endif
 
 obj-$(CONFIG_FREEZER) += freezer.o
-- 
1.5.6.5

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


Re: [PATCH][for 2.6.28] Remove -mno-spe flags as they dont belong

2008-11-15 Thread Steven Rostedt

Kumar Gala wrote:

For some unknown reason at Steven Rostedt added in disabling of the SPE
instruction generation for e500 based PPC cores in commit
6ec562328fda585be2d7f472cfac99d3b44d362a.
  


The unknown reason was that my PPC64 failed to compile without it ;-) It 
was unknown because I forgot to mention that in the change log (my bad).


On Monday, I'll apply this patch and make sure that my PPC64 still compiles.

-- Steve


We are removing it because:

1. It generates e500 kernels that don't work
2. its not the correct set of flags to do this
3. we handle this in the arch/powerpc/Makefile already
4. its unknown in talking to Steven why he did this

Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
 kernel/Makefile |4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/kernel/Makefile b/kernel/Makefile
index 9a3ec66..19fad00 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -11,8 +11,6 @@ obj-y = sched.o fork.o exec_domain.o panic.o printk.o \
hrtimer.o rwsem.o nsproxy.o srcu.o semaphore.o \
notifier.o ksysfs.o pm_qos_params.o sched_clock.o
 
-CFLAGS_REMOVE_sched.o = -mno-spe

-
 ifdef CONFIG_FUNCTION_TRACER
 # Do not trace debug files and internal ftrace files
 CFLAGS_REMOVE_lockdep.o = -pg
@@ -21,7 +19,7 @@ CFLAGS_REMOVE_mutex-debug.o = -pg
 CFLAGS_REMOVE_rtmutex-debug.o = -pg
 CFLAGS_REMOVE_cgroup-debug.o = -pg
 CFLAGS_REMOVE_sched_clock.o = -pg
-CFLAGS_REMOVE_sched.o = -mno-spe -pg
+CFLAGS_REMOVE_sched.o = -pg
 endif
 
 obj-$(CONFIG_FREEZER) += freezer.o
  


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


USB problems in 2.6.28-rc*

2008-11-15 Thread Sean MacLennan
Anybody else seeing USB problems in the 2.6.28 kernels? The warp has a
USB 1.1 port off the 440EP processor. 

In 2.6.26 we had some problems with certain USB keys, but 2.6.27 fixed
it. However, the 2.6.28 stream broke it again before rc1. We get this
twice when you try to use the usb key:

sd 0:0:0:0: [sda] 990865 512-byte hardware sectors: (507 MB/483 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
sd 0:0:0:0: timing out command, waited 60s

It then seems to work. I haven't looked into it too much since we
aren't switching to 2.6.28 anytime soon (it breaks our Secure Digital
card driver).

But I am hoping somebody might know a quick fix... something like have
you got CONFIG_x set type answer ;)

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


Re: USB problems in 2.6.28-rc*

2008-11-15 Thread Benjamin Herrenschmidt
On Sat, 2008-11-15 at 14:42 -0500, Sean MacLennan wrote:
 Anybody else seeing USB problems in the 2.6.28 kernels? The warp has a
 USB 1.1 port off the 440EP processor. 
 
 In 2.6.26 we had some problems with certain USB keys, but 2.6.27 fixed
 it. However, the 2.6.28 stream broke it again before rc1. We get this
 twice when you try to use the usb key:

Please reports this to the linux-usb mailing list ! (You can keep this
list on CC but the main people capable to help you are over there)

Cheers,
Ben.

 sd 0:0:0:0: [sda] 990865 512-byte hardware sectors: (507 MB/483 MiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Assuming drive cache: write through
  sda: sda1
 sd 0:0:0:0: [sda] Attached SCSI removable disk
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
 sd 0:0:0:0: timing out command, waited 60s
 
 It then seems to work. I haven't looked into it too much since we
 aren't switching to 2.6.28 anytime soon (it breaks our Secure Digital
 card driver).
 
 But I am hoping somebody might know a quick fix... something like have
 you got CONFIG_x set type answer ;)
 
 Cheers,
Sean
 ___
 Linuxppc-dev mailing list
 Linuxppc-dev@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-dev

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