Hi Jason,


Signed-off-by: Jason Wu <[email protected]>
---
  recipes-bsp/hardware-definition-file/hdf.inc | 46
[....]
+do_install() {
+       fn=$(unzip -l ${S}/${HDF} | awk '{print $NF}' | grep ".bit$")
+       unzip -o ${S}/${HDF} ${fn} -d ${D}
+       [ "${fn}" == "download.bit"] || mv ${D}/${fn} ${D}/download.bit
+
+       install -d ${PLATFORM_INIT_STAGE_DIR}
+       for fn in ${PLATFORM_INIT}; do
+               unzip -o ${S}/${HDF} ${fn} -d ${PLATFORM_INIT_STAGE_DIR}
+       done


Unfortunately, the approach of peeling open the HDF file and consuming
its content is problematic.  The HDF file contents are fundamentally in
a tool dependent format, and these contents are meant to be accessed
indirectly through HSI interfaces.

Moving forward, we would like to implement a meta-xilinx-tools layer
with dependencies on Xilinx maintained tools (e.g. HSI) instead of
breaking open the HDF in this fashion.

Thanks
Manju
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to