beaglebone: drop check for meta-yocto-bsp collision

Now that meta-yocto-bsp renamed reference machine to beaglebone-yocto

Signed-off-by: Denys Dmytriyenko <denys@ti.com>

1 files changed, 0 insertions, 12 deletions

diff --git a/conf/machine/include/beaglebone.inc b/conf/machine/include/beaglebone.inc
deleted file mode 100644
index b10146d1..00000000
--- a/conf/machine/include/beaglebone.inc
+++ /dev/null
@@ -1,12 +0,0 @@
-python () {
-    layers = d.getVar("BBFILE_COLLECTIONS", True)
-    if not layers:
-        return
-    if "yoctobsp" in layers:
-        bb.fatal("\nmeta-yocto-bsp has been detected in bblayers.conf, which provides basic reference BSP for beaglebone platform. " \
-                "\nSince meta-ti provides official comprehensive BSP for TI SoCs, including beaglebone, there could be potential conflicts " \
-                "\nbetween beaglebone machine definitions available in meta-yocto-bsp and meta-ti layers. It is recommended to remove " \
-                "\nor disable meta-yocto-bsp in bblayers.conf, when using meta-ti and building for beaglebone platform. Alternatively, " \
-                "\nit is possible to build for am335x-evm with meta-ti, which is a more generic platform for Sitara AM335x SoC and " \
-                "\nalso covers beaglebone variants.")
-}