aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-imx/Makefile.boot
diff options
context:
space:
mode:
authorStefan Agner <stefan@agner.ch>2015-05-20 00:03:52 +0200
committerArnd Bergmann <arnd@arndb.de>2015-05-20 23:10:14 +0200
commit8064887e02fd684fa0576cbbcdbc29ceab125c4c (patch)
tree88f802d85811ff7e6c71832646de535e9bd5f954 /arch/arm/mach-imx/Makefile.boot
parentARM: introduce ARM_SINGLE_ARMV7M for ARMv7-M platforms (diff)
downloadlinux-dev-8064887e02fd684fa0576cbbcdbc29ceab125c4c.tar.xz
linux-dev-8064887e02fd684fa0576cbbcdbc29ceab125c4c.zip
ARM: vf610: enable Cortex-M4 configuration on Vybrid SoC
This patch allows to build the Kernel for Vybrid (VF6xx) SoC when ARMv7-M CPU is selected. The resulting image runs on the secondary Cortex-M4 core. This core has equally access to all peripherals as the main Cortex-A5 core. However, there is no resource control mechanism, hence when both cores are used simultaneously, orthogonal device tree's are required. The boot CPU is dependent on the SoC variant. The available boards use mostly variants where the Cortex-A5 is the primary and hence the boot CPU. Booting the secondary Cortex-M4 CPU needs SoC specific registers written. There is no in kernel support for this right now, a external userspace utility called "m4boot" can be used to boot the kernel: m4boot xipImage initramfs.cpio.lzo vf610m4-colibri.dtb Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'arch/arm/mach-imx/Makefile.boot')
-rw-r--r--arch/arm/mach-imx/Makefile.boot0
1 files changed, 0 insertions, 0 deletions
diff --git a/arch/arm/mach-imx/Makefile.boot b/arch/arm/mach-imx/Makefile.boot
new file mode 100644
index 000000000000..e69de29bb2d1
--- /dev/null
+++ b/arch/arm/mach-imx/Makefile.boot