KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/target/linux/mvebu/image/Makefile

202 lines
5.4 KiB
Makefile
Raw Normal View History

mvebu: add inital support for Marvell Armada XP/370 SoCs This brings in the initial support for the Marvell Armada XP/370 SoCs. Successfully tested on RD-A370-A1 and DB-MV784MP-GP boards the following interfaces: - Ethernet - SDIO - GPIOs - SATA Signed-off-by: Florian Fainelli <florian@openwrt.org> SVN-Revision: 35058
2013-01-08 22:20:16 +00:00
#
mvebu: add support for the Linksys WRT3200ACM (Rango) Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-10-13 10:52:20 +00:00
# Copyright (C) 2012-2016 OpenWrt.org
# Copyright (C) 2016 LEDE-project.org
mvebu: add inital support for Marvell Armada XP/370 SoCs This brings in the initial support for the Marvell Armada XP/370 SoCs. Successfully tested on RD-A370-A1 and DB-MV784MP-GP boards the following interfaces: - Ethernet - SDIO - GPIOs - SATA Signed-off-by: Florian Fainelli <florian@openwrt.org> SVN-Revision: 35058
2013-01-08 22:20:16 +00:00
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
image: fix jffs2(_nand) image generation Variables dependend on JFFS2_BLOCKSIZE and NANDBLOCK_SIZE are used for template generation, so need to be present before inclusion of image.mk in target image Makefiles. So move all declarations to before any includes. Fixes: r42878 ("image.mk: clean up and parallelize mkfs calls") Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 46564
2015-08-05 13:55:52 +00:00
JFFS2_BLOCKSIZE = 128k
mvebu: add inital support for Marvell Armada XP/370 SoCs This brings in the initial support for the Marvell Armada XP/370 SoCs. Successfully tested on RD-A370-A1 and DB-MV784MP-GP boards the following interfaces: - Ethernet - SDIO - GPIOs - SATA Signed-off-by: Florian Fainelli <florian@openwrt.org> SVN-Revision: 35058
2013-01-08 22:20:16 +00:00
include $(TOPDIR)/rules.mk
include $(INCLUDE_DIR)/image.mk
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
KERNEL_LOADADDR := 0x00008000
mvebu: Add sub-profiles In order to support the various board NAND layout that we support, introduce a sub-profile similar to the one used by ar71xx. These subprofiles provide a default implementation for most of the building functions, while allowing each sub-profile to override any of these operations in order to have a more specific behaviour, like Mamba expects for example. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44261
2015-02-05 11:22:43 +00:00
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
define Build/dtb
$(call Image/BuildDTB,$(DTS_DIR)/$(DEVICE_DTS).dts,$@.dtb)
endef
define Build/clearfog-bundle
mvebu: rework ClearFog bundle.tar.gz generation Instead of introducing a fake filesystem type, move the tar generation step directly into the image build step. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-14 17:24:56 +00:00
rm -f $@.new
$(TAR) -cp --numeric-owner --owner=0 --group=0 --sort=name \
$(if $(SOURCE_DATE_EPOCH),--mtime="@$(SOURCE_DATE_EPOCH)") \
--file=$@.new -C $(TARGET_DIR)/ .
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
$(TAR) -rp --numeric-owner --owner=0 --group=0 --sort=name \
$(if $(SOURCE_DATE_EPOCH),--mtime="@$(SOURCE_DATE_EPOCH)") \
mvebu: rework ClearFog bundle.tar.gz generation Instead of introducing a fake filesystem type, move the tar generation step directly into the image build step. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-14 17:24:56 +00:00
--file=$@.new -C $(dir $(IMAGE_KERNEL)) $(notdir $(IMAGE_KERNEL)) $(notdir $(IMAGE_KERNEL).dtb)
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
gzip -9n -c $@.new > $@
endef
mvebu: add sdcard image creation script Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
2016-08-09 13:23:24 +00:00
# SD-Card Images:
# these values are optimized for a 4GB labeled sdcard that actually holds 7744512 sectors of 512 byte
# MBR: 2048 sectors
# Partition 1: 32768 sectors
# Partition 2: 98304 sectors (configurable)
define Build/boot-scr
rm -f $@.bootscript
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.script $@.bootscript
endef
define Build/boot-img
rm -f $@.boot
mkfs.fat -C $@.boot 16384
$(foreach dts,$(DEVICE_DTS), mcopy -i $@.boot $(DTS_DIR)/$(dts).dtb ::$(dts).dtb)
mcopy -i $@.boot $(IMAGE_KERNEL) ::zImage
mcopy -i $@.boot $@.bootscript ::boot.scr
endef
define Build/sdcard-img
ROOTFS_SIZE=$$(( $(CONFIG_TARGET_ROOTFS_PARTSIZE) * 1024 * 2 )); \
mvebu: use ext4/f2fs overlay filesystem for solidrun clearfog Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-09-08 12:19:34 +00:00
./gen_mvebu_sdcard_img.sh $@ \
uboot-mvebu: also install into KDIR to ensure it packaged in IB The clearfog image requires u-boot, so package it into KDIR to make sure it is available in imageBuilder. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
2016-09-23 11:45:21 +00:00
"$(KDIR)/openwrt-mvebu-clearfog-u-boot-spl.kwb" \
mvebu: add sdcard image creation script Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
2016-08-09 13:23:24 +00:00
c 32768 $@.boot \
mvebu: use ext4/f2fs overlay filesystem for solidrun clearfog Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-09-08 12:19:34 +00:00
83 $$ROOTFS_SIZE $(IMAGE_ROOTFS)
mvebu: add sdcard image creation script Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
2016-08-09 13:23:24 +00:00
endef
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
define Device/Default
mvebu: limit image builds to profile selection Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-26 06:36:45 +00:00
PROFILES := Default
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
DEVICE_DTS := $(1)
BOARD_NAME = $$(DEVICE_DTS)
KERNEL_NAME := zImage
KERNEL := kernel-bin | append-dtb | uImage none
build squashfs on ubi and SysupgradeNAND images Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41360
2014-06-27 13:00:25 +00:00
endef
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
define Device/UBI
IMAGES := sysupgrade.bin
build: rename sysupgrade-nand to sysupgrade-tar Now that the "sysupgrade-nand" step is used by non-NAND targets as well, rename it to "sysupgrade-tar" to make it more generic. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-07-29 13:05:51 +00:00
IMAGE/sysupgrade.bin := sysupgrade-tar
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
endef
define Device/UBI-factory
$(Device/UBI)
build: drop UBI EOF marker from images by default Only add them where they are actually required. Should help with compatibility issues with stock U-Boot images that access UBI Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-09-12 16:20:50 +00:00
UBINIZE_OPTS := -E 5
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
IMAGES += factory.img
image: remove padding parameter from append-kernel/append-rootfs Using pad-to instead of passing the optional padding to append-kernel or append-rootfs. It could be that the value of a variable is passed. In case the variable is empty no error is thrown. Furthermore the purpose of the extra parameter is hard to get without reading the code. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-11 17:05:20 +00:00
IMAGE/factory.img := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-ubi | pad-to $$$$(PAGESIZE)
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
endef
define Device/NAND-128K
$(Device/UBI)
image: use k as unit suffix for blocksize Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-04 06:56:05 +00:00
BLOCKSIZE := 128k
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
PAGESIZE := 2048
SUBPAGESIZE := 512
VID_HDR_OFFSET := 2048
endef
define Device/NAND-256K
$(Device/UBI)
image: use k as unit suffix for blocksize Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-04 06:56:05 +00:00
BLOCKSIZE := 256k
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
PAGESIZE := 4096
endef
define Device/NAND-512K
$(Device/UBI)
image: use k as unit suffix for blocksize Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-04 06:56:05 +00:00
BLOCKSIZE := 512k
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
PAGESIZE := 4096
endef
define Device/linksys
DEVICE_TITLE := Linksys $(1)
DEVICE_PACKAGES := kmod-mwlwifi wpad-mini swconfig
endef
define Device/armada-385-linksys
$(Device/NAND-128K)
$(Device/UBI-factory)
KERNEL_SIZE := 6144k
endef
define Device/linksys-wrt1200ac
$(call Device/linksys,WRT1200AC (Caiman))
$(Device/armada-385-linksys)
DEVICE_DTS := armada-385-linksys-caiman
endef
TARGET_DEVICES += linksys-wrt1200ac
define Device/linksys-wrt1900acv2
$(call Device/linksys,WRT1900ACv2 (Cobra))
$(Device/armada-385-linksys)
DEVICE_DTS := armada-385-linksys-cobra
endef
TARGET_DEVICES += linksys-wrt1900acv2
mvebu: add support for the Linksys WRT3200ACM (Rango) Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-10-13 10:52:20 +00:00
define Device/linksys-wrt3200acm
$(call Device/linksys,WRT3200ACM (Rango))
$(Device/armada-385-linksys)
DEVICE_DTS := armada-385-linksys-rango
endef
TARGET_DEVICES += linksys-wrt3200acm
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
define Device/linksys-wrt1900acs
$(call Device/linksys,WRT1900ACS (Shelby))
$(Device/armada-385-linksys)
DEVICE_DTS := armada-385-linksys-shelby
endef
TARGET_DEVICES += linksys-wrt1900acs
define Device/linksys-wrt1900ac
$(call Device/linksys,WRT1900AC (Mamba))
DEVICE_DTS := armada-xp-linksys-mamba
$(Device/NAND-128K)
$(Device/UBI-factory)
KERNEL_SIZE := 3072k
endef
TARGET_DEVICES += linksys-wrt1900ac
define Device/openblocks-ax3
$(Device/UBI-factory)
DEVICE_DTS := armada-xp-openblocks-ax3-4
image: use k as unit suffix for blocksize Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-04 06:56:05 +00:00
BLOCKSIZE := 128k
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
PAGESIZE := 1
mvebu: fix OpenBlocks AX3 image The KERNEL_SIZE variable is unset and no padding is applied. This looks like a typo to me since the ubinized image need to be aligned to the flash blocksize. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-11 17:06:32 +00:00
IMAGE/factory.img := append-kernel | pad-to $$(BLOCKSIZE) | append-ubi
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
DEVICE_TITLE := Plat'Home OpenBlocks AX3
endef
TARGET_DEVICES += openblocks-ax3
define Device/armada-385-db-ap
$(Device/NAND-256K)
$(Device/UBI-factory)
KERNEL_SIZE := 8192k
DEVICE_TITLE := Marvell Armada 385 DB AP (DB-88F6820-AP)
endef
TARGET_DEVICES += armada-385-db-ap
define Device/marvell-nand
$(Device/NAND-512K)
DEVICE_TITLE := Marvell Armada $(1)
endef
Device/armada-370-db = $(call Device/marvell-nand,370 DB (DB-88F6710-BP-DDR3))
Device/armada-370-rd = $(call Device/marvell-nand,370 RD (RD-88F6710-A1))
Device/armada-xp-db = $(call Device/marvell-nand,XP DB (DB-78460-BP))
Device/armada-xp-gp = $(call Device/marvell-nand,XP GP (DB-MV784MP-GP))
TARGET_DEVICES += armada-370-db armada-370-rd armada-xp-db armada-xp-gp
define Device/armada-388-rd
DEVICE_TITLE := Marvell Armada 388 RD (RD-88F6820-AP)
IMAGES := firmware.bin
image: remove padding parameter from append-kernel/append-rootfs Using pad-to instead of passing the optional padding to append-kernel or append-rootfs. It could be that the value of a variable is passed. In case the variable is empty no error is thrown. Furthermore the purpose of the extra parameter is hard to get without reading the code. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-11 17:05:20 +00:00
IMAGE/firmware.bin := append-kernel | pad-to 256k | append-rootfs | pad-rootfs
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
endef
TARGET_DEVICES += armada-388-rd
define Device/armada-388-clearfog
KERNEL_INSTALL := 1
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
KERNEL := dtb | kernel-bin
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
DEVICE_TITLE := SolidRun ClearFog
mvebu: add sysupgrade support for clearfog Add and enable sysupgrade support for clearfog boards, based on how the brcm2708 target does it. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
2016-09-26 10:02:40 +00:00
DEVICE_PACKAGES := mkf2fs e2fsprogs swconfig kmod-fs-vfat kmod-nls-cp437 kmod-nls-iso8859-1
mvebu: add sdcard image creation script Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
2016-08-09 13:23:24 +00:00
IMAGES := bundle.tar.gz sdcard.img.gz
mvebu: rework ClearFog bundle.tar.gz generation Instead of introducing a fake filesystem type, move the tar generation step directly into the image build step. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-14 17:24:56 +00:00
IMAGE/bundle.tar.gz := clearfog-bundle
mvebu: add sdcard image creation script Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
2016-08-09 13:23:24 +00:00
IMAGE/sdcard.img.gz := boot-scr | boot-img | sdcard-img | gzip
mvebu: add ClearFog .tar.gz bundle The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-08-11 15:20:54 +00:00
IMAGE_NAME = $$(IMAGE_PREFIX)-$$(2)
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
endef
TARGET_DEVICES += armada-388-clearfog
define Device/globalscale-mirabox
$(Device/NAND-512K)
DEVICE_DTS := armada-370-mirabox
DEVICE_TITLE := Globalscale Mirabox
mvebu: add inital support for Marvell Armada XP/370 SoCs This brings in the initial support for the Marvell Armada XP/370 SoCs. Successfully tested on RD-A370-A1 and DB-MV784MP-GP boards the following interfaces: - Ethernet - SDIO - GPIOs - SATA Signed-off-by: Florian Fainelli <florian@openwrt.org> SVN-Revision: 35058
2013-01-08 22:20:16 +00:00
endef
mvebu: switch to the new image build code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-20 08:04:03 +00:00
TARGET_DEVICES += globalscale-mirabox
mvebu: add inital support for Marvell Armada XP/370 SoCs This brings in the initial support for the Marvell Armada XP/370 SoCs. Successfully tested on RD-A370-A1 and DB-MV784MP-GP boards the following interfaces: - Ethernet - SDIO - GPIOs - SATA Signed-off-by: Florian Fainelli <florian@openwrt.org> SVN-Revision: 35058
2013-01-08 22:20:16 +00:00
$(eval $(call BuildImage))
Reference in a new issue Copy permalink