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>
master
Ryan Mounce 7 years ago committed by Hauke Mehrtens
parent 99cf825b06
commit 1cd3e9c07c
  1. 8
      target/linux/mvebu/image/Makefile

@ -192,13 +192,9 @@ define Device/armada-388-clearfog-base
KERNEL_INSTALL := 1 KERNEL_INSTALL := 1
KERNEL := kernel-bin KERNEL := kernel-bin
DEVICE_TITLE := SolidRun ClearFog Base DEVICE_TITLE := SolidRun ClearFog Base
DEVICE_PACKAGES := \ DEVICE_PACKAGES := mkf2fs e2fsprogs kmod-fs-vfat kmod-nls-cp437 kmod-nls-iso8859-1
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
IMAGES := sdcard.img.gz 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) IMAGE_NAME = $$(IMAGE_PREFIX)-$$(2)
DEVICE_DTS := armada-388-clearfog-pro armada-388-clearfog-base DEVICE_DTS := armada-388-clearfog-pro armada-388-clearfog-base
endef endef

Loading…
Cancel
Save