[meta-xilinx] Integration of PL device in the Device Tree (Yocto)

[SMITH Peter T]

No it’s quite new I think there is a page on Xilinx’s Wiki if you search in Google. It basically automates the Xilinx SDK flow i.e. HDF -> DTS but also generates all the artefacts that make up BOOT.bin.

From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-bounces at yoctoproject.org] On Behalf Of Giuseppe Di Guglielmo
Sent: 19 April 2017 19:54
To: meta-xilinx at yoctoproject.org
Subject: Re: [meta-xilinx] Integration of PL device in the Device Tree (Yocto)

Peter, I am giving a look at it.

I could not find a "guide" for using it (I am new to Yocto thus I need a little support). Do you have any pointer?

On Wed, Apr 19, 2017 at 2:49 PM, Giuseppe Di Guglielmo <giuseppe.diguglielmo at gmail.com<mailto:giuseppe.diguglielmo at gmail.com>> wrote:
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 <jeff.dagenais at gmail.com<mailto:jeff.dagenais at gmail.com>> wrote:

On Apr 19, 2017, at 14:35, Giuseppe Di Guglielmo <giuseppe.diguglielmo at gmail.com<mailto:giuseppe.diguglielmo at gmail.com>> 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<http://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!




________________________________
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20170419/056646f3/attachment.html>