Jeff, I do not know yet if I want to go to that extent. For sure, I have my own PL devices and their device drivers. I was wondering if there is a stardar way in Yocto to patch: build/tmp/work/zc702_zynq7-poky-linux-gnueabi/u-boot-xlnx/v2016.07-xilinx-v2016.3+gitAUTOINC+95e11f6eb4-r0/git/arch/arm/dts/zynq-zc702.dts (for example) with my own DTS node for a specific PL device.
Peter, I am On Wed, Apr 19, 2017 at 2:42 PM, Jean-Francois Dagenais < [email protected]> wrote: > > On Apr 19, 2017, at 14:35, Giuseppe Di Guglielmo < > [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
