summaryrefslogtreecommitdiff
path: root/meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass
diff options
context:
space:
mode:
authorPatrick Williams <patrick@stwcx.xyz>2021-10-26 14:47:53 +0300
committerPatrick Williams <patrick@stwcx.xyz>2021-10-27 00:08:02 +0300
commitb6d590af3f28f1737ff681ed0ed94d812878962c (patch)
tree59cdd5c1003468ef563cd0b4d0426cf38d04f715 /meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass
parent7bf39c061342ec43d4fe59d041858515a5afca92 (diff)
downloadopenbmc-b6d590af3f28f1737ff681ed0ed94d812878962c.tar.xz
meta-xilinx: remove subtree
The meta-xilinx layer was used for a now-deleted EVB. Neither the EVB nor the meta-xilinx layer have been updated for the Yocto override syntax change and the meta-xilinx still doesn't have a hardknott or honister branch (or corresponding support). I've asked the Xilinx maintainer back in May on when a hardknott version would be supported and I was told "about a month from now". I followed up in August and was told "work is in progress". As of today there are still zero commits in meta-xilinx since January 2021. As such, I do not believe this layer is well-maintained and we have no specific use for it anymore. Remove it until someone finds a good reason to include it and the upstream shows signs of life. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id14ea55db2ac2779edf42e63cb57ad7d25172ad5
Diffstat (limited to 'meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass')
-rw-r--r--meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass51
1 files changed, 0 insertions, 51 deletions
diff --git a/meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass b/meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass
deleted file mode 100644
index 562f3263e..000000000
--- a/meta-xilinx/meta-xilinx-bsp/classes/image-wic-utils.bbclass
+++ /dev/null
@@ -1,51 +0,0 @@
-# Helper/utility functions to work with the IMAGE_BOOT_FILES variable and its
-# expected behvaior with regards to the contents of the DEPLOY_DIR_IMAGE.
-#
-# The use of these functions assume that the deploy directory is populated with
-# any dependent files/etc. Such that the recipe using these functions depends
-# on the recipe that provides the files being used/queried.
-
-def boot_files_split_expand(d):
- # IMAGE_BOOT_FILES has extra renaming info in the format '<source>;<target>'
- for f in (d.getVar("IMAGE_BOOT_FILES") or "").split(" "):
- parts = f.split(";", 1)
- sources = [parts[0].strip()]
- if "*" in parts[0]:
- # has glob part
- import glob
- deployroot = d.getVar("DEPLOY_DIR_IMAGE")
- sources = []
- for i in glob.glob(os.path.join(deployroot, parts[0])):
- sources.append(os.path.basename(i))
-
- # for all sources, yield an entry
- for s in sources:
- if len(parts) == 2:
- yield s, parts[1].strip()
- yield s, s
-
-def boot_files_bitstream(d):
- expectedfiles = [("bitstream", True)]
- expectedexts = [(".bit", True), (".bin", False)]
- # search for bitstream paths, use the renamed file. First matching is used
- for source, target in boot_files_split_expand(d):
- # skip boot.bin and u-boot.bin, it is not a bitstream
- skip = ["boot.bin", "u-boot.bin"]
- if source in skip or target in skip:
- continue
-
- for e, t in expectedfiles:
- if source == e or target == e:
- return target, t
- for e, t in expectedexts:
- if source.endswith(e) or target.endswith(e):
- return target, t
- return "", False
-
-def boot_files_dtb_filepath(d):
- dtbs = (d.getVar("IMAGE_BOOT_FILES") or "").split(" ")
- for source, target in boot_files_split_expand(d):
- if target.endswith(".dtb"):
- return target
- return ""
-