We have our own layer that we layer above meta-xilinx and meta-xilinx-tools. We have a semi hybrid model where we use petalinux-config to generate the components and meta-plnx-generated layer. We then use straight bitbake commands to regenerate hdf artifacts, u-boot, atf, pmu, and linux fitimages.
It works nice. Took a while to get just right. Wish we didn't have to use petalinux-config though. Rich From: [email protected] [mailto:[email protected]] On Behalf Of Jean-Francois Dagenais Sent: Wednesday, April 19, 2017 1:42 PM To: Giuseppe Di Guglielmo <[email protected]> Cc: [email protected] Subject: Re: [meta-xilinx] Integration of PL device in the Device Tree (Yocto) On Apr 19, 2017, at 14:35, Giuseppe Di Guglielmo <[email protected]<mailto:[email protected]>> wrote: I am familiar with the "manula" flow for the device tree compilation (dts/dtsi, dct, etc.) but I do not know how to integrate my own device using the Yocto flow. I am using a Zynq (zc702) board. Do you have any reference or suggestion? We have a forked clone of the linux-xlnx kernel where we maintain our custom (including PL nodes) dts file. It makes sense since we also maintain custom drivers and mods. I mad a linux-abc recipe which is copied from linux-yocto-custom.bb, then I use defconfigs. I manually have to track which linux repo sha-1 I use when I change my kernel or merge in linux-xlnx changes, as well as have to observe how the resulting .config of meta-xilinx's linux-xlnx recipe changes to maintain our defconfigs. It's a trade-off. For me the advantage is full control and very easy to predict and change. Cheers!
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
