Skip to contentSkip to conversation

arm-bsp: Remove unused kernel recipe

PATCH New Jon Mason 2 participants 3 messages Aug 19, 2020

lore
Share & tools
lore

Jon Mason

author
#0 lore raw

PATCH 1/1 arm-bsp: Remove unused kernel recipe

Change-Id I4203a6d4536702a701055b511fc2b9a27868082f
---
 .../recipes-kernel/linux/linux-linaro-arm_4.19.bb     |  7 -------
 .../linux/linux-linaro-arm_4.19.bbappend              | 11 -----------
 2 files changed, 18 deletions(-)
 delete mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-linaro-arm_4.19.bb
 delete mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-linaro-arm_4.19.bbappend
meta-arm-bsp/recipes-kernel/linux/linux-linaro-arm_4.19.bb deleted +0 -7
deleted file mode 100644
index df8ba4d..0000000
@@ -1,7 +0,0 @@
-SRCREV ?= "e97e8d868aba53467039dbef3b7436c857433ae3"
-SRCREV_meta ?= "69022e62eb6c7046c84dace4af66ee8a30865865"
-
-KBRANCH ?= "latest-4.19-armlt-19.01"
-KMETA_BRANCH ?= "yocto-4.19"
-
-require linux-linaro-arm.inc
meta-arm-bsp/recipes-kernel/linux/linux-linaro-arm_4.19.bbappend deleted +0 -11
deleted file mode 100644
index b1bc72e..0000000
@@ -1,11 +0,0 @@
-# Add support for Arm Platforms (boards or simulators)
-
-require linux-arm-platforms.inc
-
-KCONF_BSP_AUDIT_LEVEL = "2"
-
-# Functionality flags
-KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
-KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
-KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
-KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ptest", " features/scsi/scsi-debug.scc", "" ,d)}"
Signature · 1 line
2.17.1
author
#1 lore raw

PATCH 1/1 arm-bsp: Correct documentation errors

Documentation for FVP and Foundation is incorrect in names and missing a field.

Change-Id I58de54e9d0883671166102e657f53cfad14a2cba
---
 meta-arm-bsp/documentation/foundation-armv8.md | 3 ++-
 meta-arm-bsp/documentation/fvp-base.md         | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)
meta-arm-bsp/documentation/foundation-armv8.md +2 -1
index 1097550..7e73da5 100644
@@ -30,9 +30,10 @@ Once done, do the following to build and run an image:
 ```
 bash$ ./Foundation_Platform --cores=4 --no-sve --gicv3 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/bl1-fvp.bin@0x0 \
+         --data=${YOCTO_DEPLOY_IMGS_DIR}/fip-fvp.bin@0x8000000 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/Image@0x80080000 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/foundation-v8-gicv3-psci.dtb@0x83000000 \
-         --block-device=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img \
+         --block-device=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img
 ```
 
 If you have built a configuration without a ramdisk, you can use the following
meta-arm-bsp/documentation/fvp-base.md +1 -1
index 0936c19..58604e1 100644
@@ -34,7 +34,7 @@ bash$ ./FVP_Base_RevC-2xAEMv8A -C bp.virtio_net.enabled=1 \
          -C bp.flashloader0.fname=${YOCTO_DEPLOY_IMGS_DIR}/fip-fvp.bin \
          --data cluster0.cpu0=${YOCTO_DEPLOY_IMGS_DIR}/Image@0x80080000 \
          --data cluster0.cpu0=${YOCTO_DEPLOY_IMGS_DIR}/fvp-base-gicv3-psci-custom.dtb@0x83000000 \
-         -C bp.virtioblockdevice.image_path=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img \
+         -C bp.virtioblockdevice.image_path=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-fvp-base.disk.img
 ```
 
 
Signature · 1 line
2.17.1
#2 lore raw

Re: [meta-arm] [PATCH] arm-bsp: Correct documentation errors

Quoted 5 lines · Jon Mason

Documentation for FVP and Foundation is incorrect in names and missing a field.

Change-Id I58de54e9d0883671166102e657f53cfad14a2cba

Pulled into master.

Thanks,
Jon

Quoted 39 lines
---
 meta-arm-bsp/documentation/foundation-armv8.md | 3 ++-
 meta-arm-bsp/documentation/fvp-base.md         | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)
meta-arm-bsp/documentation/foundation-armv8.md +2 -1
index 1097550..7e73da5 100644
@@ -30,9 +30,10 @@ Once done, do the following to build and run an image:
 ```
 bash$ ./Foundation_Platform --cores=4 --no-sve --gicv3 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/bl1-fvp.bin@0x0 \
+         --data=${YOCTO_DEPLOY_IMGS_DIR}/fip-fvp.bin@0x8000000 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/Image@0x80080000 \
          --data=${YOCTO_DEPLOY_IMGS_DIR}/foundation-v8-gicv3-psci.dtb@0x83000000 \
-         --block-device=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img \
+         --block-device=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img
 ```
 
 If you have built a configuration without a ramdisk, you can use the following
meta-arm-bsp/documentation/fvp-base.md +1 -1
index 0936c19..58604e1 100644
@@ -34,7 +34,7 @@ bash$ ./FVP_Base_RevC-2xAEMv8A -C bp.virtio_net.enabled=1 \
          -C bp.flashloader0.fname=${YOCTO_DEPLOY_IMGS_DIR}/fip-fvp.bin \
          --data cluster0.cpu0=${YOCTO_DEPLOY_IMGS_DIR}/Image@0x80080000 \
          --data cluster0.cpu0=${YOCTO_DEPLOY_IMGS_DIR}/fvp-base-gicv3-psci-custom.dtb@0x83000000 \
-         -C bp.virtioblockdevice.image_path=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-foundation-armv8.disk.img \
+         -C bp.virtioblockdevice.image_path=${YOCTO_DEPLOY_IMGS_DIR}/core-image-minimal-fvp-base.disk.img
 ```
 
 
Signature · 1 line
2.17.1