MPC821 support and PPC patches from Andrew Bray <andy@madhouse.demon.co.uk>:

  In c/src/exec/score/cpu/powerpc/rtems/score/ppc.h:

    A lot of hardware interrupts were omitted.  Patch enclosed.
    I have also added the 821.

  In c/src/exec/score/cpu/powerpc/rtems/score/cpu.h:

    My patch adds the 821.

  In c/src/exec/score/cpu/powerpc/cpu.c:

    I have added the MPC821, and also fixed up for the missing hardware
    interrupts.  It is also inconsistent with
    c/src/lib/libcpu/powerpc/mpc860/vectors/vectors.S.  This has been fixed.


  In c/src/lib/libcpu/powerpc/mpc860/vectors/vectors.S:

    Fixed an inconsistency with cpu.c.

    I also include some new files to go with the above patches.  These are the
    cpu library rtems-19990331/c/src/lib/libcpu/powerpc/mpc821/* and
    c/src/exec/score/cpu/powerpc/mpc821.h which are minor modifications of
    the 860 equivalents.

  Other comments:

    The various accesses to the DPRAM on the 860 are done with a linktime
    symbol. This could be done dynamically at run time by reading the immr
    register, and masking off the lower 16 bits.  This takes the same amount
    of time as loading an address constant, and the same number of
    instructions as well (2).

    In c/src/lib/libcpu/powerpc/mpc860/console-generic/console-generic.c:

      This will silently fail if you attempt to use SCC1.  This is only relevant
      if you are not using SCC1 for ethernet.

      This file also sets one of port B output pins for each port.  This is NOT
      generic, it should be in the BSP specific console driver.

1 files changed, 20 insertions, 0 deletions

diff --git a/c/src/lib/libcpu/powerpc/mpc821/vectors/README b/c/src/lib/libcpu/powerpc/mpc821/vectors/README
new file mode 100644
index 0000000000..536e221f43
--- /dev/null
+++ b/c/src/lib/libcpu/powerpc/mpc821/vectors/README
@@ -0,0 +1,20 @@
+#
+#  $Id$
+#
+
+The location of the vectors file object is critical.
+
+From the comments at the head of vectors.s:
+
+  The issue with this file is getting it loaded at the right place.
+  The first vector MUST be at address 0x????0100.
+  How this is achieved is dependant on the tool chain.
+
+...
+
+  The variable 'PPC_VECTOR_FILE_BASE' must be defined to be the
+  offset from 0x????0000 to the first location in the file.  This
+  will be either 0x0000 or 0xfff0.
+
+The eth_comm BSP defines PPC_VECTOR_FILE_BASE to be 0x00000000
+