Derive a new IPC buffer cap when inserting into the initial threads TCB to remove mapping information

For any other thread setting the IPC buffer via TCB_Configure will result
in a derived capability being installed that does not have mapping information.
This leads to a expected behaviour that setting a new IPC buffer (even if it is
the same as the current one), will not perform an unmapping.

Remove trailing whitespace, and align comments.

Odroid XU3 support

The gic400 used on the Exynos5 platforms is a little different from
the pl390, and needs a few small changes.

The XU3 uses a 5422 which for seL4's purposes is almost the same as
the Odroid XU's 5410.  Define a new PLAT_EXYNOS54XX to cover both.

Keep PLAT_EXYNOS5410 and ...5422 for the few places (not in the
kernel) where the difference matters.

syscall stub generator: change CapDataType into a generic BitFieldType for using bitfield generated types in generated invocations

Prior to this commit there was an unfortunate disagreement between the seL4
project build system and the kernel's Makefile. V=3 was interpreted as maximum
verbosity by the project build system and minimum verbosity by the kernel's
Makefile. This commit makes V=3 the maximum verbosity for both.

JIRA: VER-159

Initialise the 'ret' struct from a constant zero struct to ensure that no
uninitialised data is returned. Returning uninitialized data creates headaches
for binary verification.

This function is inlined in builds I have looked at, and the 'ret' struct is
never built, so this change has zero impact on the binary.

Set default MAX_NUM_BOOTINFO_DEVICE_REGIONS to a value that will fit into the initial boot info frame

The c-parser can now parse these functions, but it does it by
discarding the inline ASM block, creating a misleading and likely
malformed function body. It is better to not translate these
with a DONT_TRANSLATE comment.

This change has been made for the current verification platform
only, and should probably be extended to any other verification
targets as necessary.

(state before release on 29 July 2014)

The IFC6410 has too many devices to fit into the bootinfo page.
What is more, some are aligned on half-page boundaries.

Exclude devices on half-page boundaries from the bootinfo device list.

Suggested by @jserv on https://github.com/seL4/seL4/issues/1

arm: Perform additional cache clean to prevent TLB walker loading garbage entries for first user process

Very useful with python3 as the default platform.

Do not discard user PYTHONPATH when building

The in-kernel-directory Makefile was trying to reset CFLAGS, and
sometimes sets them to conflict with the ones set by the Kbuild system.

Only set CFLAGS and ASFLAGS for standalone builds.
(standalone builds are only really supported for KZM anyway).

Different version of GCC need diffferent combinations of -mcpu
-mtune= and -march to build properly for KZM (armv6) and cortex-a8

Make CFLAGS and ASFLAGS consistent, and rely on GCC knowing which arch is which
wwhen told what CPU to build for.

For the toolchain we have, armv6 is incompatible with cpu=arm1136jf-2, but
with cpu-cortex-a?, arch=armv7-a is required.