Separate the architecture config file and function script.

 /trunk/kconfig/kconfig.mk   |   46    23    23     0 +++++++++++++++++++++++-----------------------
 /trunk/scripts/crosstool.sh |    2     1     1     0 +-
 /trunk/docs/overview.txt    |   28    11    17     0 +++++++++++-----------------
 3 files changed, 35 insertions(+), 41 deletions(-)

1 files changed, 25 insertions, 0 deletions

diff --git a/config/arch/powerpc.in b/config/arch/powerpc.in
new file mode 100644
index 00000000..448065a5
--- /dev/null
+++ b/config/arch/powerpc.in
@@ -0,0 +1,25 @@
+# powerpc specific configuration file
+
+config ARCH_powerpc
+    select ARCH_SUPPORT_ABI
+    select ARCH_SUPPORT_CPU
+    select ARCH_SUPPORT_TUNE
+    help
+      The PowerPC architecture, as defined by:
+        http://www.ibm.com/developerworks/eserver/articles/archguide.html
+
+config ARCH_POWERPC_SPE
+    bool
+    prompt "Enable SPE support"
+    default n
+    help
+      Add support for the Signal Processing Engine.  This will set up
+      the toolchain so that it supports the SPE ABI extensions. This
+      mainly targets Freescale e500 processors.
+
+      Setting this option will append "spe" to the end of your target
+      tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
+      configure/build system will know to include SPE ABI support.
+      It will also automatically add "-mabi=spe -mspe" to your
+      TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
+      so you do not need to explicitly add them.