aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRyan Mounce <ryan@mounce.com.au>2017-10-01 20:14:02 +1030
committerHauke Mehrtens <hauke@hauke-m.de>2017-10-15 00:24:22 +0200
commit1cd3e9c07cf4622f000f919071b77197b23fe118 (patch)
tree60f4fc71418136e68a04d22439f46e146d716e96
parent99cf825b06d08912a14b4ba213700c2a558bf888 (diff)
downloadupstream-1cd3e9c07cf4622f000f919071b77197b23fe118.tar.gz
upstream-1cd3e9c07cf4622f000f919071b77197b23fe118.tar.bz2
upstream-1cd3e9c07cf4622f000f919071b77197b23fe118.zip
mvebu: clean up ClearFog Base package selection
It is unclear why so many packages are selected for ClearFog Base compared to its big brother, and there is no reason to not append metadata for Base. Tidy this up as the only hardware difference between Base/Pro is the presence of a switch and a different board name / device tree. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
-rw-r--r--target/linux/mvebu/image/Makefile8
1 files changed, 2 insertions, 6 deletions
diff --git a/target/linux/mvebu/image/Makefile b/target/linux/mvebu/image/Makefile
index 322e0c12c6..f0c4b09c9e 100644
--- a/target/linux/mvebu/image/Makefile
+++ b/target/linux/mvebu/image/Makefile
@@ -192,13 +192,9 @@ define Device/armada-388-clearfog-base
KERNEL_INSTALL := 1
KERNEL := kernel-bin
DEVICE_TITLE := SolidRun ClearFog Base
- DEVICE_PACKAGES := \
- kmod-nls-cp437 kmod-nls-iso8859-1 \
- mkf2fs e2fsprogs kmod-fs-vfat kmod-fuse kmod-fs-f2fs \
- kmod-ata-core kmod-ata-ahci kmod-ata-marvell-sata kmod-scsi-core kmod-scsi-generic \
- kmod-button-hotplug kmod-gpio-button-hotplug
+ DEVICE_PACKAGES := mkf2fs e2fsprogs kmod-fs-vfat kmod-nls-cp437 kmod-nls-iso8859-1
IMAGES := sdcard.img.gz
- IMAGE/sdcard.img.gz := boot-scr-cfbase | boot-img | sdcard-img | gzip
+ IMAGE/sdcard.img.gz := boot-scr-cfbase | boot-img | sdcard-img | gzip | append-metadata
IMAGE_NAME = $$(IMAGE_PREFIX)-$$(2)
DEVICE_DTS := armada-388-clearfog-pro armada-388-clearfog-base
endef