diff --git a/.gitignore b/.gitignore
index c07a6d31e485bf01a925e110e56d35fc30b24c32..1db00d73714737526eb56a325c7113a55f0bd6ff 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,68 +1,2 @@
-# Git files
-*.orig
-
-# Prerequisites
-*.d
-
-# Compiled Object files
-*.o
-*.x
-*.lo
-*.obj
-*.slo
-*.objdump
-
-# Precompiled Headers
-*.gch
-*.pch
-
-# Compiled Dynamic libraries
-*.so
-*.dll
-*.dylib
-
-# Fortran module files
-*.mod
-*.smod
-
-# Compiled Static libraries
-*.a
-*.la
-*.lai
-*.lib
-
-# Executables
-*.exe
-*.out
-*.app
-*.elf
-
-# Vim
-*.swp
-
-# Code
-.vscode
-
-# Binary files
-*.hex
-*.dat
-*.pdf
-*.png
-*.bin
-*.doc
-*.docx
-
-# Misc files
-*.htm
-*.csv
-*.ini
-*.xml
-*.log
-*.bak
-*.BAK*
-*.html
-*.setup
-*.stackdump
-
-# Build directories
-**/build*/**
+*
+!README.md
diff --git a/.gitmodules b/.gitmodules
index 3abc8cf19fab218711fa9af873c0a246bb9e33c3..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 100644
--- a/.gitmodules
+++ b/.gitmodules
@@ -1,9 +0,0 @@
-[submodule "poky"]
- path = poky
- url = https://git.yoctoproject.org/git/poky
-[submodule "meta-openembedded"]
- path = meta-openembedded
- url = https://github.com/openembedded/meta-openembedded.git
-[submodule "meta-intel-fpga"]
- path = meta-intel-fpga
- url = https://git.yoctoproject.org/meta-intel-fpga
diff --git a/meta-fpga-iot/conf/layer.conf b/meta-fpga-iot/conf/layer.conf
deleted file mode 100644
index 9976991063eabb7c7d1abc7fc6a66fd487a9cc1c..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/conf/layer.conf
+++ /dev/null
@@ -1,14 +0,0 @@
-# We have a conf and classes directory, append to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have a recipes directory, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "meta-fpga-iot"
-BBFILE_PATTERN_meta-fpga-iot := "^${LAYERDIR}/"
-# increase the number
-BBFILE_PRIORITY_meta-fpga-iot = "11"
-LAYERSERIES_COMPAT_meta-fpga-iot = "kirkstone"
-
-# yves
-BBDEBUG = "yes"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/COPYING.MIT b/meta-fpga-iot/meta-a10soc-devkit/COPYING.MIT
deleted file mode 100644
index 89de354795ec7a7cdab07c091029653d3618540d..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/meta-fpga-iot/meta-a10soc-devkit/README b/meta-fpga-iot/meta-a10soc-devkit/README
deleted file mode 100644
index 8284b7a0c359a593da63f5494abc28bd928f5696..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/README
+++ /dev/null
@@ -1,41 +0,0 @@
-This README file contains information on the contents of the meta-de0-nano layer.
-
-Please see the corresponding sections below for details.
-
-Dependencies
-============
-
- URI: <first dependency>
- branch: <branch name>
-
- URI: <second dependency>
- branch: <branch name>
-
- .
- .
- .
-
-Patches
-=======
-
-Please submit any patches against the meta-de0-nano layer to the xxxx mailing list (xxxx@zzzz.org)
-and cc: the maintainer:
-
-Maintainer: XXX YYYYYY <xxx.yyyyyy@zzzzz.com>
-
-Table of Contents
-=================
-
- I. Adding the meta-de0-nano layer to your build
- II. Misc
-
-
-I. Adding the meta-de0-nano layer to your build
-=================================================
-
-Run 'bitbake-layers add-layer meta-de0-nano'
-
-II. Misc
-========
-
---- replace with specific information about the meta-de0-nano layer ---
diff --git a/meta-fpga-iot/meta-a10soc-devkit/conf/bblayers.conf.sample b/meta-fpga-iot/meta-a10soc-devkit/conf/bblayers.conf.sample
deleted file mode 100644
index fe2b2e8e557a628d9227b0d88308b3748ce4fda2..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/conf/bblayers.conf.sample
+++ /dev/null
@@ -1,21 +0,0 @@
-# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
-# changes incompatibly
-LCONF_VERSION = "7"
-
-BBPATH = "${TOPDIR}"
-BBFILES ?= ""
-
-BBLAYERS ?= " \
- ##OEROOT##/meta \
- ##OEROOT##/meta-poky \
- ##OEROOT##/meta-yocto-bsp \
- ##OEROOT##/../meta-openembedded/meta-oe \
- ##OEROOT##/../meta-openembedded/meta-networking \
- ##OEROOT##/../meta-openembedded/meta-webserver \
- ##OEROOT##/../meta-openembedded/meta-perl \
- ##OEROOT##/../meta-openembedded/meta-python \
- ##OEROOT##/../meta-intel-fpga \
- ##OEROOT##/../meta-fpga-iot \
- ##OEROOT##/../meta-fpga-iot/meta-common \
- ##OEROOT##/../meta-fpga-iot/meta-a10soc-devkit \
-"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/conf/conf-notes.txt b/meta-fpga-iot/meta-a10soc-devkit/conf/conf-notes.txt
deleted file mode 100644
index 2e5ece1500aa6507474a154c33d7ed5b56cc052e..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/conf/conf-notes.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-Common targets are:
- core-image
- core-image-minimal
- core-image-minimal-dev
- ==> fpga-iot-image
diff --git a/meta-fpga-iot/meta-a10soc-devkit/conf/layer.conf b/meta-fpga-iot/meta-a10soc-devkit/conf/layer.conf
deleted file mode 100644
index 30c7362173c3db61427e01c83cff2514c03808d6..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have recipes-* directories, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "meta-a10soc-devkit"
-#BBFILE_PATTERN_meta-a10soc-devkit := "^${LAYERDIR}/"
-BBFILE_PATTERN_meta-a10soc-devkit := "^${LAYERDIR}/"
-BBFILE_PRIORITY_meta-a10soc-devkit = "12"
-
-LAYERSERIES_COMPAT_meta-a10soc-devkit = "${LAYERSERIES_COMPAT_core}"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/conf/local.conf.sample b/meta-fpga-iot/meta-a10soc-devkit/conf/local.conf.sample
deleted file mode 100644
index 85b2d4e86c7967a9b415df5b140360092102b9a7..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/conf/local.conf.sample
+++ /dev/null
@@ -1,295 +0,0 @@
-#
-# This file is your local configuration file and is where all local user settings
-# are placed. The comments in this file give some guide to the options a new user
-# to the system might want to change but pretty much any configuration option can
-# be set in this file. More adventurous users can look at
-# local.conf.sample.extended which contains other examples of configuration which
-# can be placed in this file but new users likely won't need any of them
-# initially.
-#
-# Lines starting with the '#' character are commented out and in some cases the
-# default values are provided as comments to show people example syntax. Enabling
-# the option is a question of removing the # character and making any change to the
-# variable as required.
-
-#
-# Machine Selection
-#
-# You need to select a specific machine to target the build with. There are a selection
-# of emulated machines available which can boot and run in the QEMU emulator:
-#
-MACHINE ?= "a10soc-devkit"
-#
-# This sets the default machine to be qemux86-64 if no other machine is selected:
-MACHINE ??= "qemux86-64"
-
-#
-# Where to place downloads
-#
-# During a first build the system will download many different source code tarballs
-# from various upstream projects. This can take a while, particularly if your network
-# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
-# can preserve this directory to speed up this part of subsequent builds. This directory
-# is safe to share between multiple builds on the same machine too.
-#
-# The default is a downloads directory under TOPDIR which is the build directory.
-#
-#DL_DIR ?= "${TOPDIR}/downloads"
-
-#
-# Where to place shared-state files
-#
-# BitBake has the capability to accelerate builds based on previously built output.
-# This is done using "shared state" files which can be thought of as cache objects
-# and this option determines where those files are placed.
-#
-# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
-# from these files if no changes were made to the configuration. If changes were made
-# to the configuration, only shared state files where the state was still valid would
-# be used (done using checksums).
-#
-# The default is a sstate-cache directory under TOPDIR.
-#
-#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
-
-#
-# Where to place the build output
-#
-# This option specifies where the bulk of the building work should be done and
-# where BitBake should place its temporary files and output. Keep in mind that
-# this includes the extraction and compilation of many applications and the toolchain
-# which can use Gigabytes of hard disk space.
-#
-# The default is a tmp directory under TOPDIR.
-#
-#TMPDIR = "${TOPDIR}/tmp"
-
-#
-# Default policy config
-#
-# The distribution setting controls which policy settings are used as defaults.
-# The default value is fine for general Yocto project use, at least initially.
-# Ultimately when creating custom policy, people will likely end up subclassing
-# these defaults.
-#
-DISTRO ?= "poky"
-# As an example of a subclass there is a "bleeding" edge policy configuration
-# where many versions are set to the absolute latest code from the upstream
-# source control systems. This is just mentioned here as an example, its not
-# useful to most new users.
-# DISTRO ?= "poky-bleeding"
-
-#
-# Package Management configuration
-#
-# This variable lists which packaging formats to enable. Multiple package backends
-# can be enabled at once and the first item listed in the variable will be used
-# to generate the root filesystems.
-# Options are:
-# - 'package_deb' for debian style deb files
-# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
-# - 'package_rpm' for rpm style packages
-# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
-# We default to rpm:
-PACKAGE_CLASSES ?= "package_rpm"
-
-#
-# SDK target architecture
-#
-# This variable specifies the architecture to build SDK items for and means
-# you can build the SDK packages for architectures other than the machine you are
-# running the build on (i.e. building i686 packages on an x86_64 host).
-# Supported values are i686, x86_64, aarch64
-#SDKMACHINE ?= "i686"
-
-#
-# Extra image configuration defaults
-#
-# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
-# images. Some of these options are added to certain image types automatically. The
-# variable can contain the following options:
-# "dbg-pkgs" - add -dbg packages for all installed packages
-# (adds symbol information for debugging/profiling)
-# "src-pkgs" - add -src packages for all installed packages
-# (adds source code for debugging)
-# "dev-pkgs" - add -dev packages for all installed packages
-# (useful if you want to develop against libs in the image)
-# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
-# (useful if you want to run the package test suites)
-# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
-# "tools-debug" - add debugging tools (gdb, strace)
-# "eclipse-debug" - add Eclipse remote debugging support
-# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
-# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
-# "debug-tweaks" - make an image suitable for development
-# e.g. ssh root access has a blank password
-# There are other application targets that can be used here too, see
-# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
-# We default to enabling the debugging tweaks.
-#EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
-
-#
-# Additional image features
-#
-# The following is a list of additional classes to use when building images which
-# enable extra features. Some available options which can be included in this variable
-# are:
-# - 'buildstats' collect build statistics
-USER_CLASSES ?= "buildstats"
-
-#
-# Runtime testing of images
-#
-# The build system can test booting virtual machine images under qemu (an emulator)
-# after any root filesystems are created and run tests against those images. It can also
-# run tests against any SDK that are built. To enable this uncomment these lines.
-# See classes/test{image,sdk}.bbclass for further details.
-#IMAGE_CLASSES += "testimage testsdk"
-#TESTIMAGE_AUTO:qemuall = "1"
-
-#
-# Interactive shell configuration
-#
-# Under certain circumstances the system may need input from you and to do this it
-# can launch an interactive shell. It needs to do this since the build is
-# multithreaded and needs to be able to handle the case where more than one parallel
-# process may require the user's attention. The default is iterate over the available
-# terminal types to find one that works.
-#
-# Examples of the occasions this may happen are when resolving patches which cannot
-# be applied, to use the devshell or the kernel menuconfig
-#
-# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
-# Note: currently, Konsole support only works for KDE 3.x due to the way
-# newer Konsole versions behave
-#OE_TERMINAL = "auto"
-# By default disable interactive patch resolution (tasks will just fail instead):
-PATCHRESOLVE = "noop"
-
-#
-# Disk Space Monitoring during the build
-#
-# Monitor the disk space during the build. If there is less that 1GB of space or less
-# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
-# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard halt
-# of the build. The reason for this is that running completely out of space can corrupt
-# files and damages the build in ways which may not be easily recoverable.
-# It's necessary to monitor /tmp, if there is no space left the build will fail
-# with very exotic errors.
-BB_DISKMON_DIRS ??= "\
- STOPTASKS,${TMPDIR},1G,100K \
- STOPTASKS,${DL_DIR},1G,100K \
- STOPTASKS,${SSTATE_DIR},1G,100K \
- STOPTASKS,/tmp,100M,100K \
- HALT,${TMPDIR},100M,1K \
- HALT,${DL_DIR},100M,1K \
- HALT,${SSTATE_DIR},100M,1K \
- HALT,/tmp,10M,1K"
-
-#
-# Shared-state files from other locations
-#
-# As mentioned above, shared state files are prebuilt cache data objects which can be
-# used to accelerate build time. This variable can be used to configure the system
-# to search other mirror locations for these objects before it builds the data itself.
-#
-# This can be a filesystem directory, or a remote url such as https or ftp. These
-# would contain the sstate-cache results from previous builds (possibly from other
-# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
-# cache locations to check for the shared objects.
-# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
-# at the end as shown in the examples below. This will be substituted with the
-# correct path within the directory structure.
-#SSTATE_MIRRORS ?= "\
-#file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
-#file://.* file:///some/local/dir/sstate/PATH"
-
-#
-# Yocto Project SState Mirror
-#
-# The Yocto Project has prebuilt artefacts available for its releases, you can enable
-# use of these by uncommenting the following lines. This will mean the build uses
-# the network to check for artefacts at the start of builds, which does slow it down
-# equally, it will also speed up the builds by not having to build things if they are
-# present in the cache. It assumes you can download something faster than you can build it
-# which will depend on your network.
-# Note: For this to work you also need hash-equivalence passthrough to the matching server
-#
-#BB_HASHSERVE_UPSTREAM = "hashserv.yocto.io:8687"
-#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"
-
-#
-# Qemu configuration
-#
-# By default native qemu will build with a builtin VNC server where graphical output can be
-# seen. The line below enables the SDL UI frontend too.
-PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
-# By default libsdl2-native will be built, if you want to use your host's libSDL instead of
-# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
-#ASSUME_PROVIDED += "libsdl2-native"
-
-# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
-# a handy set of menus for controlling the emulator.
-#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+"
-
-#
-# Hash Equivalence
-#
-# Enable support for automatically running a local hash equivalence server and
-# instruct bitbake to use a hash equivalence aware signature generator. Hash
-# equivalence improves reuse of sstate by detecting when a given sstate
-# artifact can be reused as equivalent, even if the current task hash doesn't
-# match the one that generated the artifact.
-#
-# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
-#
-#BB_HASHSERVE = "auto"
-#BB_SIGNATURE_HANDLER = "OEEquivHash"
-
-#
-# Memory Resident Bitbake
-#
-# Bitbake's server component can stay in memory after the UI for the current command
-# has completed. This means subsequent commands can run faster since there is no need
-# for bitbake to reload cache files and so on. Number is in seconds, after which the
-# server will shut down.
-#
-#BB_SERVER_TIMEOUT = "60"
-
-# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
-# track the version of this file when it was generated. This can safely be ignored if
-# this doesn't mean anything to you.
-CONF_VERSION = "2"
-
-# Set the root password to 'fpgai0t'
-INHERIT += "extrausers"
-# To generate the password hash run: mkpasswd -m sha-512 fpgai0t -s "11223344"
-EXTRA_USERS_PARAMS = " \
- usermod -p '\$6\$11223344\$VIywnBJNxOjsWY7SweEjH0T3zJlSpIssk3xxMMUpg.XKLcGazn0/7iGDXP7d6wyVyLi0u/ziD/0ALWv4DblFs/' root; \
-"
-
-# Uncomment and edit when more users are required, pass=ChangeMe!
-# To generate the password hash run: mkpasswd -m sha-512 ChangeMe! -s "11223344"
-#EXTRA_USERS_PARAMS += " useradd -m user1; \
-# useradd -m user2; \
-# usermod -p '\$6\$11223344\$qN2jYvVmyPj2MMm5vMEYxUTWN4ABErw1M/YD.0jYA4mK2qnRPNU5evCtIhIBO/Xzmc1sJDcoCv7X/8N16XfCm1' user1; \
-# usermod -p '\$6\$11223344\$qN2jYvVmyPj2MMm5vMEYxUTWN4ABErw1M/YD.0jYA4mK2qnRPNU5evCtIhIBO/Xzmc1sJDcoCv7X/8N16XfCm1' user2; \
-# usermod -a -G sudo user1; \
-# usermod -a -G sudo user2; "
-
-# dbus-sensors uses CMake downloads for package manager.
-# Exports below provide the proxy variables to all recipes:
-export http_proxy
-export HTTP_PROXY
-export https_proxy
-export HTTPS_PROXY
-export no_proxy
-export NO_PROXY
-
-#
-# Use systemd for system initialization
-#
-DISTRO_FEATURES:append = " systemd"
-DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
-VIRTUAL-RUNTIME_init_manager = "systemd"
-VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/conf/machine/a10soc-devkit.conf b/meta-fpga-iot/meta-a10soc-devkit/conf/machine/a10soc-devkit.conf
deleted file mode 100644
index cf54879ffb2d3d9c768ba171d441023312a3df22..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/conf/machine/a10soc-devkit.conf
+++ /dev/null
@@ -1,53 +0,0 @@
-require conf/machine/include/socfpga.inc
-
-SPL_BINARY = "spl/u-boot-splx4.sfp"
-UBOOT_BINARY = "u-boot.img"
-
-# TBD: check if required
-PREFERRED_PROVIDER_virtual/bootloader = "u-boot-socfpga"
-PREFERRED_VERSION_u-boot-socfpga ?= "v2022.04%"
-# end of TBD
-
-UBOOT_CONFIG ??= "arria10-socdk"
-UBOOT_CONFIG[arria10-socdk] = "socfpga_arria10_defconfig"
-
-KMACHINE = "arria10"
-
-# Default kernel devicetrees
-KERNEL_DEVICETREE ?= "\
- a10soc-devkit.dtb \
- "
-
-EXTRA_IMAGECMD:jffs2 ?= "-n -q \
- ${@bb.utils.contains("IMAGE_TYPE", "nand", "-e 0x20000 -s 0x200", "", d)} \
- ${@bb.utils.contains("IMAGE_TYPE", "qspi", "-e 0x10000", "", d)} \
- "
-
-SERIAL_CONSOLES ?= "115200;ttyS0"
-
-UBOOT_EXTLINUX ?= "1"
-UBOOT_EXTLINUX_LABELS ?= "default"
-UBOOT_EXTLINUX_DEFAULT_LABEL ?= "Arria10 SOCDK SDMMC"
-
-UBOOT_EXTLINUX_MENU_DESCRIPTION:default ?= "Arria10 SOCDK SDMMC"
-UBOOT_EXTLINUX_KERNEL_IMAGE:default ?= "../${KERNEL_IMAGETYPE}"
-UBOOT_EXTLINUX_FDTDIR:default ?= ".."
-UBOOT_EXTLINUX_CONSOLE ?= "console=ttyS0,115200n8"
-UBOOT_EXTLINUX_KERNEL_ARGS:default ?= "rootwait rw earlyprintk memmap=16M$0x3F000000"
-UBOOT_EXTLINUX_ROOT:default ?= "root=/dev/mmcblk0p2"
-
-IMAGE_BOOT_FILES ?= " \
- ${KERNEL_DEVICETREE} \
- ${KERNEL_IMAGETYPE} \
- ${UBOOT_BINARY} \
- extlinux.conf;extlinux/extlinux.conf \
- "
-
-# Build both Image and zImage for Arria10
-KERNEL_ALT_IMAGETYPE = "Image"
-
-WKS_FILE ?= "sdimage-fpga-iot-a10soc-devkit.wks"
-IMAGE_FSTYPES:append = " wic"
-
-PREFERRED_PROVIDER_virtual/kernel = "linux-socfpga-lts"
-PREFERRED_VERSION_linux-socfpga-lts ?= "5.15%"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg b/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg
deleted file mode 100644
index 1ff58caa6e1b85626a74e30c401c65d924aa502e..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg
+++ /dev/null
@@ -1,2 +0,0 @@
-CONFIG_USE_BOOTCOMMAND=y
-CONFIG_BOOTCOMMAND="fatload mmc 0:1 ${loadaddr} soc_system.core.rbf; fpga load 0 ${loadaddr} ${filesize}; bridge enable; run bootcmd_mmc0"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend b/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend
deleted file mode 100644
index aa4eed3abc5a1f40d2f49813c9eed2da032b4d17..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend
+++ /dev/null
@@ -1,6 +0,0 @@
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://bootcmd.cfg \
-"
-
-PROVIDES += "u-boot"
diff --git a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/a10soc-devkit.dts b/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/a10soc-devkit.dts
deleted file mode 100644
index c668860f38e7f37b5bbfaf135240493bff6fe7ce..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/a10soc-devkit.dts
+++ /dev/null
@@ -1,43 +0,0 @@
-/*
- * TODO
- */
-
-/dts-v1/;
-#include "socfpga_arria10_socdk_sdmmc.dts"
-#include <dt-bindings/gpio/gpio.h>
-
-/ {
- aliases {
- };
-
- chosen {
- };
-
-/*
- * Add GPIO configuration for Altera PIO IP.
- * Adjust Avalon MM address if needed.
- */
- soc {
- gpio_altr0: gpio@ff230000 {
- compatible = "altr,pio-1.0";
- reg = <0xff230000 0x10>;
- altr,ngpio = <8>;
- #gpio-cells = <2>;
- gpio-controller;
- gpio-line-names = "GPIO0_0","GPIO0_1","GPIO0_2","GPIO0_3","GPIO0_4","GPIO0_5","GPIO0_6","GPIO0_7";
- status = "disabled";
- };
- };
-
-/*
- * 1-Wire temperature sensor (DS18B20)
- */
- soc {
- ds18b20 {
- compatible = "w1-gpio";
- gpios = <&gpio_altr0 0 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>;
- status = "disabled";
- };
- };
-
-};
diff --git a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/test.cfg b/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/test.cfg
deleted file mode 100644
index 38803fcc8a8cc5749e5e510e4df6541367e2fc90..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts/test.cfg
+++ /dev/null
@@ -1,3 +0,0 @@
-CONFIG_GPIO_ALTERA=m
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
diff --git a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts_%.bbappend b/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
deleted file mode 100644
index 4a29f596d67e9ff7f0753408cfaf766ff9a3513b..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-COMPATIBLE_MACHINE_${MACHINE} = "a10soc-devkit"
-
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-
-SRC_URI += "file://a10soc-devkit.dts;subdir=git/arch/arm/boot/dts \
-"
-
-# Add Kernel config with required configuration about features disabling or enabling
-# SRC_URI += "file://test.cfg "
diff --git a/meta-fpga-iot/meta-a10soc-devkit/wic/sdimage-fpga-iot-a10soc-devkit.wks b/meta-fpga-iot/meta-a10soc-devkit/wic/sdimage-fpga-iot-a10soc-devkit.wks
deleted file mode 100644
index c6d65637feadde34e3549265f7e2964680560d0b..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-a10soc-devkit/wic/sdimage-fpga-iot-a10soc-devkit.wks
+++ /dev/null
@@ -1,8 +0,0 @@
-# short-description: Create an SD card image for the Arria 10 SoC.
-# long-description: Create an SD card image for the Arria 10 SoC.
-# Boot files are located in the first vfat partition and u-Boot is located in
-# the third partition.
-
-part --source bootimg-partition --ondisk mmcblk --fstype=vfat --mkfs-extraopts "-F 32" --label boot --active --align 1024 --fixed-size 500M --system-id b
-part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 1024 --fixed-size 1500M
-part --source rawcopy --sourceparams="file=u-boot-splx4.sfp" --ondisk mmcblk --system-id=a2 --align 1024 --fixed-size 10M
diff --git a/meta-fpga-iot/meta-common/COPYING.MIT b/meta-fpga-iot/meta-common/COPYING.MIT
deleted file mode 100644
index fb950dc69feb8afa93493747f33d6e1c02659b55..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/meta-fpga-iot/meta-common/README b/meta-fpga-iot/meta-common/README
deleted file mode 100644
index a1b76f9ad1b286728bf62cf5f304d85be2c4967f..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/README
+++ /dev/null
@@ -1,41 +0,0 @@
-This README file contains information on the contents of the meta-common layer.
-
-Please see the corresponding sections below for details.
-
-Dependencies
-============
-
- URI: <first dependency>
- branch: <branch name>
-
- URI: <second dependency>
- branch: <branch name>
-
- .
- .
- .
-
-Patches
-=======
-
-Please submit any patches against the meta-common layer to the xxxx mailing list (xxxx@zzzz.org)
-and cc: the maintainer:
-
-Maintainer: XXX YYYYYY <xxx.yyyyyy@zzzzz.com>
-
-Table of Contents
-=================
-
- I. Adding the meta-common layer to your build
- II. Misc
-
-
-I. Adding the meta-common layer to your build
-=================================================
-
-Run 'bitbake-layers add-layer meta-common'
-
-II. Misc
-========
-
---- replace with specific information about the meta-common layer ---
diff --git a/meta-fpga-iot/meta-common/conf/layer.conf b/meta-fpga-iot/meta-common/conf/layer.conf
deleted file mode 100644
index 5a4d75f61476dfacb381203fab1de46f433f0481..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have recipes-* directories, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes*/*/*.bb \
- ${LAYERDIR}/recipes*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "meta-common"
-BBFILE_PATTERN_meta-common = ""
-BBFILE_PRIORITY_meta-common = "11"
-
-LAYERSERIES_COMPAT_meta-common = "kirkstone"
diff --git a/meta-fpga-iot/meta-common/recipes-common/data-xfers-test-app/data-xfers-test-app.bb b/meta-fpga-iot/meta-common/recipes-common/data-xfers-test-app/data-xfers-test-app.bb
deleted file mode 100644
index 9d93e19a09878731d47538ae0d118e8470cdedbd..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-common/data-xfers-test-app/data-xfers-test-app.bb
+++ /dev/null
@@ -1,12 +0,0 @@
-SUMMARY = "Test application to demonstrate data transfers"
-
-SRC_URI = "git://github.com/zbychl/data-xfers-test-app.git;protocol=https;branch=main"
-SRCREV = "${AUTOREV}"
-PV = "0.1+git${SRCPV}"
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=43fda83878573685622d1a78886759ca"
-
-S = "${WORKDIR}/git"
-
-inherit cmake
diff --git a/meta-fpga-iot/meta-common/recipes-common/test-app/files/test-app.service b/meta-fpga-iot/meta-common/recipes-common/test-app/files/test-app.service
deleted file mode 100644
index f8a6d56870b47b355029526dd869ef891452b102..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-common/test-app/files/test-app.service
+++ /dev/null
@@ -1,9 +0,0 @@
-[Unit]
-Description=Test App/Service
-
-[Service]
-ExecStart=/usr/bin/test-app
-Restart=on-failure
-
-[Install]
-WantedBy=multi-user.target
diff --git a/meta-fpga-iot/meta-common/recipes-common/test-app/test-app.bb b/meta-fpga-iot/meta-common/recipes-common/test-app/test-app.bb
deleted file mode 100644
index 02defc25999e511b4decc543fb4fd2b0e6423297..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-common/test-app/test-app.bb
+++ /dev/null
@@ -1,24 +0,0 @@
-SUMMARY = "Test application"
-
-SRC_URI = "git://github.com/zbychl/test-app.git;protocol=https;branch=main"
-SRCREV = "${AUTOREV}"
-PV = "0.1+git${SRCPV}"
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=43fda83878573685622d1a78886759ca"
-
-S = "${WORKDIR}/git"
-
-# Enable when used for service
-#SRC_URI += "file://test-app.service "
-#SYSTEMD_SERVICE:${PN} += "test-app.service"
-#DEPENDS = "systemd "
-#do_install:append () {
-# install -d ${D}${systemd_system_unitdir}
-# install -m 0644 ${WORKDIR}/test-app.service ${D}${systemd_system_unitdir}
-#}
-
-inherit cmake
-
-# Enable when used for service
-#inherit systemd
diff --git a/meta-fpga-iot/meta-common/recipes-connectivity/openssh/openssh_%.bbappend b/meta-fpga-iot/meta-common/recipes-connectivity/openssh/openssh_%.bbappend
deleted file mode 100644
index e02ba198dcd681bd8e458dc118235d6b74ffa04b..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-connectivity/openssh/openssh_%.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-
-do_install:append () {
-# Enable root logging
- sed -i -e 's:#PermitRootLogin prohibit-password:PermitRootLogin yes:' ${D}${sysconfdir}/ssh/sshd_config
-}
-
diff --git a/meta-fpga-iot/meta-common/recipes-core/images/fpga-iot-image.bb b/meta-fpga-iot/meta-common/recipes-core/images/fpga-iot-image.bb
deleted file mode 100644
index 1727b746d6ae470f0d83652809408db88030e64e..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-core/images/fpga-iot-image.bb
+++ /dev/null
@@ -1,51 +0,0 @@
-DESCRIPTION = "Base FPGA IoT image, based on core-image."
-
-IMAGE_FEATURES += " splash ssh-server-openssh "
-
-IMAGE_INSTALL = " \
- packagegroup-core-boot \
- packagegroup-core-full-cmdline \
- ${CORE_IMAGE_EXTRA_INSTALL} \
-"
-
-inherit core-image
-
-IMAGE_INSTALL:append = " \
- socat i2c-tools mtd-utils \
- bash coreutils util-linux devmem2 systemd dhcpcd \
- libgpiod libgpiod-tools test-app data-xfers-test-app \
-"
-
-# For MQTT
-IMAGE_INSTALL:append = " \
- mosquitto \
-"
-
-# For gcc, g++, make, stdlib, etc.
-IMAGE_INSTALL:append = " \
- packagegroup-core-buildessential \
- cmake \
-"
-
-# For Python3 and packages
-IMAGE_INSTALL:append = " \
- python3 python3-pip python3-cryptography python3-numpy python3-paho-mqtt \
-"
-
-# For Wireshark
-IMAGE_INSTALL:append = " \
- wireshark tshark \
-"
-
-IMAGE_INSTALL:append = " \
- dtc \
-"
-
-# For Apache
-IMAGE_INSTALL:append = " \
- apache2 \
-"
-
-IMAGE_FEATURES:append = " "
-
-IMAGE_FSTYPES += " jffs2 squashfs-xz"
diff --git a/meta-fpga-iot/meta-common/recipes-core/systemd/systemd/00-fpga-iot-eth0.network b/meta-fpga-iot/meta-common/recipes-core/systemd/systemd/00-fpga-iot-eth0.network
deleted file mode 100644
index 02e068cb7c8da8602413c0510979bcb68ab9300e..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-core/systemd/systemd/00-fpga-iot-eth0.network
+++ /dev/null
@@ -1,10 +0,0 @@
-[Match]
-Name=eth0
-[Network]
-DHCP=ipv4
-LinkLocalAddressing=no
-#Address=192.168.1.2
-#Gateway=192.168.1.1
-
-[Link]
-#MACAddress=66:55:44:33:22:11
diff --git a/meta-fpga-iot/meta-common/recipes-core/systemd/systemd_%.bbappend b/meta-fpga-iot/meta-common/recipes-core/systemd/systemd_%.bbappend
deleted file mode 100644
index 072a18759427851fc57b80c84126b78f715e4cd0..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-core/systemd/systemd_%.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-FILESEXTRAPATHS:append := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://00-fpga-iot-eth0.network"
-
-FILES_${PN} += "${systemd_unitdir}/network/00-fpga-iot-eth0.network"
-
-do_install:append() {
- install -m 644 ${WORKDIR}/00-fpga-iot-eth0.network ${D}${sysconfdir}/systemd/network/
-}
-
diff --git a/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts/1wire-thermal-sensor.cfg b/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts/1wire-thermal-sensor.cfg
deleted file mode 100644
index 7b350eb78e3cc0b34c634eb07aeae58667ce8abd..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts/1wire-thermal-sensor.cfg
+++ /dev/null
@@ -1,3 +0,0 @@
-CONFIG_W1=y
-CONFIG_W1_MASTER_GPIO=y
-CONFIG_W1_SLAVE_THERM=y
diff --git a/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts_%.bbappend b/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
deleted file mode 100644
index 568b1f7dd702c4b53d69e3c9a4ec93d0d103fa06..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-common/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
+++ /dev/null
@@ -1,6 +0,0 @@
-COMPATIBLE_MACHINE_${MACHINE} = "de0-nano"
-
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-# Control support for 1-Wire Temperature Sensors
-SRC_URI += "file://1wire-thermal-sensor.cfg "
diff --git a/meta-fpga-iot/meta-de0-nano/COPYING.MIT b/meta-fpga-iot/meta-de0-nano/COPYING.MIT
deleted file mode 100644
index 89de354795ec7a7cdab07c091029653d3618540d..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/meta-fpga-iot/meta-de0-nano/README b/meta-fpga-iot/meta-de0-nano/README
deleted file mode 100644
index 8284b7a0c359a593da63f5494abc28bd928f5696..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/README
+++ /dev/null
@@ -1,41 +0,0 @@
-This README file contains information on the contents of the meta-de0-nano layer.
-
-Please see the corresponding sections below for details.
-
-Dependencies
-============
-
- URI: <first dependency>
- branch: <branch name>
-
- URI: <second dependency>
- branch: <branch name>
-
- .
- .
- .
-
-Patches
-=======
-
-Please submit any patches against the meta-de0-nano layer to the xxxx mailing list (xxxx@zzzz.org)
-and cc: the maintainer:
-
-Maintainer: XXX YYYYYY <xxx.yyyyyy@zzzzz.com>
-
-Table of Contents
-=================
-
- I. Adding the meta-de0-nano layer to your build
- II. Misc
-
-
-I. Adding the meta-de0-nano layer to your build
-=================================================
-
-Run 'bitbake-layers add-layer meta-de0-nano'
-
-II. Misc
-========
-
---- replace with specific information about the meta-de0-nano layer ---
diff --git a/meta-fpga-iot/meta-de0-nano/conf/bblayers.conf.sample b/meta-fpga-iot/meta-de0-nano/conf/bblayers.conf.sample
deleted file mode 100644
index d44359017e070a15c3ebf3f22fac26660686909f..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/conf/bblayers.conf.sample
+++ /dev/null
@@ -1,21 +0,0 @@
-# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
-# changes incompatibly
-LCONF_VERSION = "7"
-
-BBPATH = "${TOPDIR}"
-BBFILES ?= ""
-
-BBLAYERS ?= " \
- ##OEROOT##/meta \
- ##OEROOT##/meta-poky \
- ##OEROOT##/meta-yocto-bsp \
- ##OEROOT##/../meta-openembedded/meta-oe \
- ##OEROOT##/../meta-openembedded/meta-networking \
- ##OEROOT##/../meta-openembedded/meta-webserver \
- ##OEROOT##/../meta-openembedded/meta-perl \
- ##OEROOT##/../meta-openembedded/meta-python \
- ##OEROOT##/../meta-intel-fpga \
- ##OEROOT##/../meta-fpga-iot \
- ##OEROOT##/../meta-fpga-iot/meta-common \
- ##OEROOT##/../meta-fpga-iot/meta-de0-nano \
-"
diff --git a/meta-fpga-iot/meta-de0-nano/conf/conf-notes.txt b/meta-fpga-iot/meta-de0-nano/conf/conf-notes.txt
deleted file mode 100644
index 2e5ece1500aa6507474a154c33d7ed5b56cc052e..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/conf/conf-notes.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-Common targets are:
- core-image
- core-image-minimal
- core-image-minimal-dev
- ==> fpga-iot-image
diff --git a/meta-fpga-iot/meta-de0-nano/conf/layer.conf b/meta-fpga-iot/meta-de0-nano/conf/layer.conf
deleted file mode 100644
index 11140add2ab3a4ed0ec83ccbbf2f0ba7be6caa55..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have recipes-* directories, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "meta-de0-nano"
-#BBFILE_PATTERN_meta-de0-nano := "^${LAYERDIR}/"
-BBFILE_PATTERN_meta-de0-nano := "^${LAYERDIR}/"
-BBFILE_PRIORITY_meta-de0-nano = "12"
-
-LAYERSERIES_COMPAT_meta-de0-nano = "${LAYERSERIES_COMPAT_core}"
diff --git a/meta-fpga-iot/meta-de0-nano/conf/local.conf.sample b/meta-fpga-iot/meta-de0-nano/conf/local.conf.sample
deleted file mode 100644
index f98000cda5146b3eb432f80b5a18660d8f6267da..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/conf/local.conf.sample
+++ /dev/null
@@ -1,295 +0,0 @@
-#
-# This file is your local configuration file and is where all local user settings
-# are placed. The comments in this file give some guide to the options a new user
-# to the system might want to change but pretty much any configuration option can
-# be set in this file. More adventurous users can look at
-# local.conf.sample.extended which contains other examples of configuration which
-# can be placed in this file but new users likely won't need any of them
-# initially.
-#
-# Lines starting with the '#' character are commented out and in some cases the
-# default values are provided as comments to show people example syntax. Enabling
-# the option is a question of removing the # character and making any change to the
-# variable as required.
-
-#
-# Machine Selection
-#
-# You need to select a specific machine to target the build with. There are a selection
-# of emulated machines available which can boot and run in the QEMU emulator:
-#
-MACHINE ?= "de0-nano"
-#
-# This sets the default machine to be qemux86-64 if no other machine is selected:
-MACHINE ??= "qemux86-64"
-
-#
-# Where to place downloads
-#
-# During a first build the system will download many different source code tarballs
-# from various upstream projects. This can take a while, particularly if your network
-# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
-# can preserve this directory to speed up this part of subsequent builds. This directory
-# is safe to share between multiple builds on the same machine too.
-#
-# The default is a downloads directory under TOPDIR which is the build directory.
-#
-#DL_DIR ?= "${TOPDIR}/downloads"
-
-#
-# Where to place shared-state files
-#
-# BitBake has the capability to accelerate builds based on previously built output.
-# This is done using "shared state" files which can be thought of as cache objects
-# and this option determines where those files are placed.
-#
-# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
-# from these files if no changes were made to the configuration. If changes were made
-# to the configuration, only shared state files where the state was still valid would
-# be used (done using checksums).
-#
-# The default is a sstate-cache directory under TOPDIR.
-#
-#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
-
-#
-# Where to place the build output
-#
-# This option specifies where the bulk of the building work should be done and
-# where BitBake should place its temporary files and output. Keep in mind that
-# this includes the extraction and compilation of many applications and the toolchain
-# which can use Gigabytes of hard disk space.
-#
-# The default is a tmp directory under TOPDIR.
-#
-#TMPDIR = "${TOPDIR}/tmp"
-
-#
-# Default policy config
-#
-# The distribution setting controls which policy settings are used as defaults.
-# The default value is fine for general Yocto project use, at least initially.
-# Ultimately when creating custom policy, people will likely end up subclassing
-# these defaults.
-#
-DISTRO ?= "poky"
-# As an example of a subclass there is a "bleeding" edge policy configuration
-# where many versions are set to the absolute latest code from the upstream
-# source control systems. This is just mentioned here as an example, its not
-# useful to most new users.
-# DISTRO ?= "poky-bleeding"
-
-#
-# Package Management configuration
-#
-# This variable lists which packaging formats to enable. Multiple package backends
-# can be enabled at once and the first item listed in the variable will be used
-# to generate the root filesystems.
-# Options are:
-# - 'package_deb' for debian style deb files
-# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
-# - 'package_rpm' for rpm style packages
-# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
-# We default to rpm:
-PACKAGE_CLASSES ?= "package_rpm"
-
-#
-# SDK target architecture
-#
-# This variable specifies the architecture to build SDK items for and means
-# you can build the SDK packages for architectures other than the machine you are
-# running the build on (i.e. building i686 packages on an x86_64 host).
-# Supported values are i686, x86_64, aarch64
-#SDKMACHINE ?= "i686"
-
-#
-# Extra image configuration defaults
-#
-# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
-# images. Some of these options are added to certain image types automatically. The
-# variable can contain the following options:
-# "dbg-pkgs" - add -dbg packages for all installed packages
-# (adds symbol information for debugging/profiling)
-# "src-pkgs" - add -src packages for all installed packages
-# (adds source code for debugging)
-# "dev-pkgs" - add -dev packages for all installed packages
-# (useful if you want to develop against libs in the image)
-# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
-# (useful if you want to run the package test suites)
-# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
-# "tools-debug" - add debugging tools (gdb, strace)
-# "eclipse-debug" - add Eclipse remote debugging support
-# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
-# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
-# "debug-tweaks" - make an image suitable for development
-# e.g. ssh root access has a blank password
-# There are other application targets that can be used here too, see
-# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
-# We default to enabling the debugging tweaks.
-#EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
-
-#
-# Additional image features
-#
-# The following is a list of additional classes to use when building images which
-# enable extra features. Some available options which can be included in this variable
-# are:
-# - 'buildstats' collect build statistics
-USER_CLASSES ?= "buildstats"
-
-#
-# Runtime testing of images
-#
-# The build system can test booting virtual machine images under qemu (an emulator)
-# after any root filesystems are created and run tests against those images. It can also
-# run tests against any SDK that are built. To enable this uncomment these lines.
-# See classes/test{image,sdk}.bbclass for further details.
-#IMAGE_CLASSES += "testimage testsdk"
-#TESTIMAGE_AUTO:qemuall = "1"
-
-#
-# Interactive shell configuration
-#
-# Under certain circumstances the system may need input from you and to do this it
-# can launch an interactive shell. It needs to do this since the build is
-# multithreaded and needs to be able to handle the case where more than one parallel
-# process may require the user's attention. The default is iterate over the available
-# terminal types to find one that works.
-#
-# Examples of the occasions this may happen are when resolving patches which cannot
-# be applied, to use the devshell or the kernel menuconfig
-#
-# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
-# Note: currently, Konsole support only works for KDE 3.x due to the way
-# newer Konsole versions behave
-#OE_TERMINAL = "auto"
-# By default disable interactive patch resolution (tasks will just fail instead):
-PATCHRESOLVE = "noop"
-
-#
-# Disk Space Monitoring during the build
-#
-# Monitor the disk space during the build. If there is less that 1GB of space or less
-# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
-# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard halt
-# of the build. The reason for this is that running completely out of space can corrupt
-# files and damages the build in ways which may not be easily recoverable.
-# It's necessary to monitor /tmp, if there is no space left the build will fail
-# with very exotic errors.
-BB_DISKMON_DIRS ??= "\
- STOPTASKS,${TMPDIR},1G,100K \
- STOPTASKS,${DL_DIR},1G,100K \
- STOPTASKS,${SSTATE_DIR},1G,100K \
- STOPTASKS,/tmp,100M,100K \
- HALT,${TMPDIR},100M,1K \
- HALT,${DL_DIR},100M,1K \
- HALT,${SSTATE_DIR},100M,1K \
- HALT,/tmp,10M,1K"
-
-#
-# Shared-state files from other locations
-#
-# As mentioned above, shared state files are prebuilt cache data objects which can be
-# used to accelerate build time. This variable can be used to configure the system
-# to search other mirror locations for these objects before it builds the data itself.
-#
-# This can be a filesystem directory, or a remote url such as https or ftp. These
-# would contain the sstate-cache results from previous builds (possibly from other
-# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
-# cache locations to check for the shared objects.
-# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
-# at the end as shown in the examples below. This will be substituted with the
-# correct path within the directory structure.
-#SSTATE_MIRRORS ?= "\
-#file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
-#file://.* file:///some/local/dir/sstate/PATH"
-
-#
-# Yocto Project SState Mirror
-#
-# The Yocto Project has prebuilt artefacts available for its releases, you can enable
-# use of these by uncommenting the following lines. This will mean the build uses
-# the network to check for artefacts at the start of builds, which does slow it down
-# equally, it will also speed up the builds by not having to build things if they are
-# present in the cache. It assumes you can download something faster than you can build it
-# which will depend on your network.
-# Note: For this to work you also need hash-equivalence passthrough to the matching server
-#
-#BB_HASHSERVE_UPSTREAM = "hashserv.yocto.io:8687"
-#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"
-
-#
-# Qemu configuration
-#
-# By default native qemu will build with a builtin VNC server where graphical output can be
-# seen. The line below enables the SDL UI frontend too.
-PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
-# By default libsdl2-native will be built, if you want to use your host's libSDL instead of
-# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
-#ASSUME_PROVIDED += "libsdl2-native"
-
-# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
-# a handy set of menus for controlling the emulator.
-#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+"
-
-#
-# Hash Equivalence
-#
-# Enable support for automatically running a local hash equivalence server and
-# instruct bitbake to use a hash equivalence aware signature generator. Hash
-# equivalence improves reuse of sstate by detecting when a given sstate
-# artifact can be reused as equivalent, even if the current task hash doesn't
-# match the one that generated the artifact.
-#
-# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
-#
-#BB_HASHSERVE = "auto"
-#BB_SIGNATURE_HANDLER = "OEEquivHash"
-
-#
-# Memory Resident Bitbake
-#
-# Bitbake's server component can stay in memory after the UI for the current command
-# has completed. This means subsequent commands can run faster since there is no need
-# for bitbake to reload cache files and so on. Number is in seconds, after which the
-# server will shut down.
-#
-#BB_SERVER_TIMEOUT = "60"
-
-# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
-# track the version of this file when it was generated. This can safely be ignored if
-# this doesn't mean anything to you.
-CONF_VERSION = "2"
-
-# Set the root password to 'fpgai0t'
-INHERIT += "extrausers"
-# To generate the password hash run: mkpasswd -m sha-512 fpgai0t -s "11223344"
-EXTRA_USERS_PARAMS = " \
- usermod -p '\$6\$11223344\$VIywnBJNxOjsWY7SweEjH0T3zJlSpIssk3xxMMUpg.XKLcGazn0/7iGDXP7d6wyVyLi0u/ziD/0ALWv4DblFs/' root; \
-"
-
-# Uncomment and edit when more users are required, pass=ChangeMe!
-# To generate the password hash run: mkpasswd -m sha-512 ChangeMe! -s "11223344"
-#EXTRA_USERS_PARAMS += " useradd -m user1; \
-# useradd -m user2; \
-# usermod -p '\$6\$11223344\$qN2jYvVmyPj2MMm5vMEYxUTWN4ABErw1M/YD.0jYA4mK2qnRPNU5evCtIhIBO/Xzmc1sJDcoCv7X/8N16XfCm1' user1; \
-# usermod -p '\$6\$11223344\$qN2jYvVmyPj2MMm5vMEYxUTWN4ABErw1M/YD.0jYA4mK2qnRPNU5evCtIhIBO/Xzmc1sJDcoCv7X/8N16XfCm1' user2; \
-# usermod -a -G sudo user1; \
-# usermod -a -G sudo user2; "
-
-# dbus-sensors uses CMake downloads for package manager.
-# Exports below provide the proxy variables to all recipes:
-export http_proxy
-export HTTP_PROXY
-export https_proxy
-export HTTPS_PROXY
-export no_proxy
-export NO_PROXY
-
-#
-# Use systemd for system initialization
-#
-DISTRO_FEATURES:append = " systemd"
-DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
-VIRTUAL-RUNTIME_init_manager = "systemd"
-VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
diff --git a/meta-fpga-iot/meta-de0-nano/conf/machine/de0-nano.conf b/meta-fpga-iot/meta-de0-nano/conf/machine/de0-nano.conf
deleted file mode 100644
index 4a2c8c3775c0660ef49e1389f10dde62eab4626b..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/conf/machine/de0-nano.conf
+++ /dev/null
@@ -1,41 +0,0 @@
-require conf/machine/include/socfpga.inc
-
-PREFERRED_PROVIDER_virtual/bootloader = "u-boot-socfpga"
-PREFERRED_VERSION_u-boot-socfpga ?= "v2022.04%"
-
-UBOOT_CONFIG ??= "de0-nano-soc"
-
-UBOOT_CONFIG[de0-nano-soc] = "socfpga_de0_nano_soc_defconfig"
-
-KMACHINE = "cyclone5"
-
-# Default kernel devicetrees
-KERNEL_DEVICETREE:de0-nano ?= "\
- de0-nano.dtb \
- "
-
-SERIAL_CONSOLES ?= "115200;ttyS0"
-
-UBOOT_EXTLINUX ?= "1"
-UBOOT_EXTLINUX_LABELS ?= "default"
-UBOOT_EXTLINUX_DEFAULT_LABEL ?= "Cyclone5 SOCDK SDMMC"
-
-UBOOT_EXTLINUX_FDT:default ?= "../de0-nano.dtb"
-UBOOT_EXTLINUX_ROOT:default ?= "root=/dev/mmcblk0p3"
-UBOOT_EXTLINUX_MENU_DESCRIPTION:default ?= "Cyclone5 SOCDK SDMMC"
-UBOOT_EXTLINUX_KERNEL_IMAGE:default ?= "../${KERNEL_IMAGETYPE}"
-UBOOT_EXTLINUX_FDTDIR:default ?= "../"
-UBOOT_EXTLINUX_KERNEL_ARGS:default ?= "rootwait rw earlycon"
-
-IMAGE_BOOT_FILES ?= " \
- ${KERNEL_DEVICETREE} \
- ${KERNEL_IMAGETYPE} \
- extlinux.conf;extlinux/extlinux.conf \
- "
-
-WKS_FILE ?= "sdimage-fpga-iot-de0-nano.wks"
-IMAGE_FSTYPES +="wic"
-
-PREFERRED_PROVIDER_virtual/kernel = "linux-socfpga-lts"
-PREFERRED_VERSION_linux-socfpga-lts ?= "5.15%"
-
diff --git a/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg b/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg
deleted file mode 100644
index 2e62fc949f5db5576c182a6befdb9102904845a9..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga/bootcmd.cfg
+++ /dev/null
@@ -1,2 +0,0 @@
-CONFIG_USE_BOOTCOMMAND=y
-CONFIG_BOOTCOMMAND="fatload mmc 0:1 ${loadaddr} soc_system.rbf; fpga load 0 ${loadaddr} ${filesize}; bridge enable; run bootcmd_mmc0"
diff --git a/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend b/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend
deleted file mode 100644
index aa4eed3abc5a1f40d2f49813c9eed2da032b4d17..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/recipes-bsp/u-boot/u-boot-socfpga_%.bbappend
+++ /dev/null
@@ -1,6 +0,0 @@
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://bootcmd.cfg \
-"
-
-PROVIDES += "u-boot"
diff --git a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/de0-nano.dts b/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/de0-nano.dts
deleted file mode 100644
index 1ec71ae6ad0fa799c701ef4f54b27f5723f0047c..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/de0-nano.dts
+++ /dev/null
@@ -1,43 +0,0 @@
-/*
- * TODO
- */
-
-/dts-v1/;
-#include "socfpga_cyclone5_de0_nano_soc.dts"
-#include <dt-bindings/gpio/gpio.h>
-
-/ {
- aliases {
- };
-
- chosen {
- };
-
-/*
- * Add GPIO configuration for Altera PIO IP.
- * Adjust Avalon MM address if needed.
- */
- soc {
- gpio_altr0: gpio@ff230000 {
- compatible = "altr,pio-1.0";
- reg = <0xff230000 0x10>;
- altr,ngpio = <8>;
- #gpio-cells = <2>;
- gpio-controller;
- gpio-line-names = "GPIO0_0","GPIO0_1","GPIO0_2","GPIO0_3","GPIO0_4","GPIO0_5","GPIO0_6","GPIO0_7";
- status = "disabled";
- };
- };
-
-/*
- * 1-Wire temperature sensor (DS18B20)
- */
- soc {
- ds18b20 {
- compatible = "w1-gpio";
- gpios = <&gpio_altr0 0 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>;
- status = "disabled";
- };
- };
-
-};
diff --git a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/test.cfg b/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/test.cfg
deleted file mode 100644
index 38803fcc8a8cc5749e5e510e4df6541367e2fc90..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts/test.cfg
+++ /dev/null
@@ -1,3 +0,0 @@
-CONFIG_GPIO_ALTERA=m
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
diff --git a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts_%.bbappend b/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
deleted file mode 100644
index b9f9544dcd7e868377d16cf620c0e6f3df9c9db5..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/recipes-kernel/linux/linux-socfpga-lts_%.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-COMPATIBLE_MACHINE_${MACHINE} = "de0-nano"
-
-FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
-
-
-SRC_URI += "file://de0-nano.dts;subdir=git/arch/arm/boot/dts \
-"
-
-# Add Kernel config with required configuration about features disabling or enabling
-# SRC_URI += "file://test.cfg "
diff --git a/meta-fpga-iot/meta-de0-nano/wic/sdimage-fpga-iot-de0-nano.wks b/meta-fpga-iot/meta-de0-nano/wic/sdimage-fpga-iot-de0-nano.wks
deleted file mode 100644
index 831a582854e9539b89e00734aba2aa658ea4e373..0000000000000000000000000000000000000000
--- a/meta-fpga-iot/meta-de0-nano/wic/sdimage-fpga-iot-de0-nano.wks
+++ /dev/null
@@ -1,8 +0,0 @@
-# short-description: Create an SD card image for the Cyclone 5 and Arria 5 SoCs
-# long-description: Create an SD card image for the Cyclone 5 and Arria 5 SoCs.
-# Boot files are located in the first vfat partition and u-Boot is located in
-# the third partition.
-
-part --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4 --size 16
-part --source rawcopy --sourceparams="file=u-boot-with-spl.sfp" --ondisk mmcblk --system-id=a2 --align 4 --fixed-size 1M
-part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 --size 1G
diff --git a/meta-intel-fpga b/meta-intel-fpga
deleted file mode 160000
index 74e4dae14953f6c7ea6d49df4f8477bcb71326b2..0000000000000000000000000000000000000000
--- a/meta-intel-fpga
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit 74e4dae14953f6c7ea6d49df4f8477bcb71326b2
diff --git a/meta-openembedded b/meta-openembedded
deleted file mode 160000
index 9c5541f7e18a1fac3b8dea71e1ebb8398d58e6ff..0000000000000000000000000000000000000000
--- a/meta-openembedded
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit 9c5541f7e18a1fac3b8dea71e1ebb8398d58e6ff
diff --git a/poky b/poky
deleted file mode 160000
index ef5214f584765810e94a6f61585ccbcd9b909502..0000000000000000000000000000000000000000
--- a/poky
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit ef5214f584765810e94a6f61585ccbcd9b909502