On Tue, Jan 23, 2018 at 12:53 AM, Martin Siegumfeldt <[email protected]> wrote: > Hi, > > We are rendering a custom piece of HW based on Ultrascale+, and have the > Xilinx QEMU successfully running. An extensible SDK (eSDK) is delivered to > the application developers and to close the loop we would like to be capable > of delivering also the QEMU instance. The machine image- and qemuboot.conf is > not part of the eSDK and is thus delivered next to the eSDK. Unfortunately, > the Xilinx conf file describes a few absolute path variables (caused by e.g. > https://github.com/Xilinx/meta-xilinx/blob/73921b4a599834308fc0dadb785f395dded89f9e/meta-xilinx-bsp/conf/machine/zcu102-zynqmp.conf#L55 > I believe) prohibiting this conf file to be shared between the application > developers. AFACICS, this is in contrast to the generic QEMU machine configs > (http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/machines/) > which only describes relative path variables - I assume this is related to > the "custom" Xilinx PMU. > > Do you see any way around these absolute paths, which thus enables directly > sharing the QEMU instance with eSDK developers?
All of these files should be in the deploy directory, I don't see any reason why they need to be absolute. How do the other configs point to the images? Alistair > > Thanks, > Martin > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
