The default value is zero anyway.

Signed-off-by: Axel Heider <axelheider@gmx.de>

Enforce the maximum possible integer size in the generated C headers
instead of doing this in CMake.

Signed-off-by: Axel Heider <axel.heider@hensoldt-cyber.de>

This commit also converts our own copyright headers to directly use
SPDX, but leaves all other copyright header intact, only adding the
SPDX ident. As far as possible this commit also merges multiple
Data61 copyright statements/headers into one for consistency.

outputs all CPUs described in the DT to the elfloader
header and also includes any devices in the seL4,elfoader-devices
property.

Add required functionality for MCS.

Tickless timer drivers are yet to be implemented for

- allwinner
- apq8064
- am335x
- exynos4
- zynqmp
- imx8mm
- imx8mq

The kernel device IRQs and Frame mappings generated by this script will
only come from nodes specified in the seL4,kernel-devices property of
the chosen node.  Previously these devices were inferred by the script
but this led to false matching and didn't support easily overriding
which devices to match under different configurations or across
different platforms.

Explicitly specifying which devices from the device tree will be used in
the kernel makes it easier to check which devices the kernel is actually
using and makes it easier to change on a per platform or per
configuration basis.

Correctly defined the macros to translate between virtual and hardware
IRQs such that PPIs can be properly handled on gic_v2. It is now
possible to create a per-core handler for PPIs on platforms using this
GIC.

This explains why the DTS overlays intentionally throw away part of
the kernel memory window.

This is a hack that allows user-space tools like the capDL static
allocator to work. Otherwise, the allocator (currently unaware of the
kernel window) would think that there is a 28-bit untyped at pptr
0xf0000000, and would generate untyped derivations that are not
available at runtime.

Note that we clamp to 0xff000000 on exynos4 and exynos5, *not*
0xfff00000 (PPTR_TOP), to avoid the ASID PD hole at
0xff000000..0xff200000. The affected platforms are ARM VM platforms;
VM images are often larger than 13MiB and would overlap the ASID hole
if loaded from PPTR_TOP. init_freemem fails if this overlap exists.

This is to reflect that this driver provides support for features that
are newer than gic_pl390 such as virtualisation.

Instead of processing each platform CMake file during the arch's
config.cmake file, we process all of the platform CMake files first.
This is primarily motivated by wanting to move platform configuration
into a config file that is processed via a -C argument to the initial
build initialisation command.

Now a platform config is responsible for setting the kernel architecture
and it's own platform/arch specific config settings. Where previously a
platform was chosen in an arch specific way via either setting
KernelARMPlatform or KernelX86Sel4Arch or KernelRiscVPlatform, a
platform can now be set by KernelPlatform. In cases where a platform may
further parameterise its configuration it is free to choose its own
config options to query. Platforms that support multiple seL4
architectures should use KernelSel4Arch to query this.  Platforms that
provide sub platforms such as exynos5 and subplatforms exynos5250,
exynos5410 and exynos5422 can be selected by specifying
KernelPlatform=exynos5, KernelARMPlatform=exynos5410 for example.

Add a device tree overlay such that all memory on the exynos4 fits in
the kernel window. It's unknown if the memory past 0x50000000 is valid,
when the elf-loader attempts to write to it it hangs.

- remove unused header files replaced by declare_default_headers
- move timer.h to drivers/timer/exynos5422-mct.h
- move mct.h to drivers/timer/mct.h

Add .cmake-format.yaml which defines custom functions with kwargs to
style nicely

These are no longer necessary as we are merging all the ARM
linker scripts into common_arm.lds

Platforms affected:

Bcm2837, AM335x, Exynos4, Exynos5*, Hikey, imx31, imx6, imx7, OMAP3, TK1,
TX1, TX2, zynq7000, zynqmp.

This change moves all arm platform timers to drivers/timer
and renames them to the compatibility string specified in the dts.
Now the correct timer is included at build time based on the dts,
this follows the same pattern as the serial-refactor.
Have moved the arm generic_timer and priv_timer into the timer
folder and updated cmake configs appropriately.

Have added a drivers/serial folder to kernel, where all serial drivers
will be kept. The point is to have the the dts parsed and generate cmake
to include the right uart.c file prefixed with the compatibility.
Have removed all io.c from plat and includes from plat/config.cmake and
updated CHANGES file.

Note that the auto-generated kernel_devices will differ slightly from
the ones present in the kernel until now. When devices have
registers that aren't page-aligned we now always set the appropriate
PPTR to be the start address of the device, while previously the PPTR
was sometimes page-aligned.

Specifically, this change to PPTRs affects:
- bcm2837 intc
- bcm2837 uart
- allwinnerA20 timer

This changes all ARM platforms over to using the device tree found in
the kernel to generate memory region information.

Removed all Kbuild/Kconfig/Makefiles from the kernel as we migrate
to a CMake only build system. Kbuild is no longer supported.

- for arm generic timer platforms, we remove resetTimer ->
resetGenericTimer indirection and simply include generic_timer.h
- this reduces boiler plate for platforms that share timer drivers, as
  they simply include the one header
- there is far more timer code in the RT kernel, which motivates this
change

This prepares for inlinining the generic timer in header files, which will reduce the
redundancy for all platforms that use it.

Since mct.c shared code with the generic timer, both could not define a
resetTimer function. This commit splits the logic and definitions used
by exynos4 and exynos4* into common definitions in mct.h, with the
unique code for both in hardware.c

This commit adds an alternate build system using CMake that operates indepenently of
the existing Kconfig+Kbuild+make based build system

* move devices to static array in hardware.h
* use one higher level function to map them in.

* move p_reg functions up a level
* move p_reg definitions to hardware.h

This wraps the printfs in CONFIG_IRQ_REPORTING
and reduces redundancy.

While provided by each hardware platform this function is never called.

Originally building the kernel was largely considered to be done in
one of two ways
1. Release build with no assertions, no debug symbols and no printing.
   This was generally considered to be a 'verified' build
2. Debug build with assertions, debug symbols and printing

Since then various options were added, such as the 'code injection'
option, which we wanted on builds that did not have assertions or
other options that affected performance. As such it did not depend
upon a debug build and had large warning signs saying that enabling
this in a release build would not give you a verified or trusted
kernel.

Most recently the ability to print from the kernel in release mode
was added. For the same reason that tying the ability to print with
the performance reduction of various debugging was not always desireable.

This change attempts to unify the current state and have a single top
level option to enable a 'verification friendly' build. All other
options (assertions, printing, code injection) then depend upon
this configuration not being set.

SELFOUR-279: rename Wait -> Recv, add wrappers for seL4_Poll and seL4_Wait for notification objects.

This commit deprecates seL4_ReplyWait, removes seL4_NBwait completely,
and changes the return type of seL4_Wait to void (seL4_Wait should be
used for notification objects, and seL4_Recv should be used where
seL4_Wait was used previously for endpoints).

xIntroduce RELEASE_PRINTF, which allows a renamed printf (release_printf) to be used in a release build of the kernel - userful for debugging tests that only fail on a release build of the kernel

This covers the kernel stack, globals frame and device memory. We shouldn't be
executing in any of these pages, so functionality should be unaffected. This is
primarily a debugging aid.