From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp103.mer-nm.internl.net (smtp103.mer-nm.internl.net [217.149.192.139]) by mail.openembedded.org (Postfix) with ESMTP id 6D53161220 for ; Wed, 14 Aug 2013 14:17:04 +0000 (UTC) Received: from amavisd-new (mailscanner04.wrt-nm.internl.net [217.149.192.127]) by smtp103.mer-nm.internl.net (Postfix) with ESMTP id E76A43F59E for ; Wed, 14 Aug 2013 16:17:03 +0200 (CEST) X-Spam-scanned: scanned by InterNLnet Mail Scan System X-Spam-Flag: NO X-Spam-Score: -3.418 X-Spam-Level: X-Spam-Status: No, score=-3.418 tagged_above=-999 required=4.5 tests=[BAYES_00=-2.9, KHOP_DYNAMIC2=1, KHOP_THREADED=-1.5, RDNS_DYNAMIC=0.982, _DSLHELP01=-1] autolearn=no X-Spam-Languages: en Received: from smtp103.mer-nm.internl.net ([217.149.192.139]) by amavisd-new (mailscanner04.wrt-nm.internl.net [217.149.192.160]) (amavisd-new, port 10024) with ESMTP for ; Wed, 14 Aug 2013 16:17:03 +0200 (CEST) Received: from TOP-EX02.topic.local (82-204-13-181.dsl.bbeyond.nl [82.204.13.181]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp103.mer-nm.internl.net (Postfix) with ESMTPS for ; Wed, 14 Aug 2013 16:17:03 +0200 (CEST) Received: from TOP-EX01.TOPIC.LOCAL (192.168.10.102) by mail.topic.nl (192.168.1.103) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 14 Aug 2013 16:16:57 +0200 Received: from [192.168.80.45] (192.168.80.45) by TOP-EX01.TOPIC.LOCAL (192.168.10.102) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 14 Aug 2013 16:17:02 +0200 Message-ID: <520B915E.2080506@topic.nl> Date: Wed, 14 Aug 2013 16:17:02 +0200 From: Mike Looijmans User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: References: <1376401955-5676-1-git-send-email-otavio@ossystems.com.br> In-Reply-To: <1376401955-5676-1-git-send-email-otavio@ossystems.com.br> X-Originating-IP: [192.168.80.45] X-EXCLAIMER-MD-CONFIG: 9833cda7-5b21-4d34-9a38-8d025ddc3664 X-EXCLAIMER-MD-BIFURCATION-INSTANCE: 0 Subject: Re: [PATCH v2] linux-dtb: Use kernel build system to generate the dtb files X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Aug 2013 14:17:04 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable =EF=BB=BF On 08/13/2013 03:52 PM, Otavio Salvador wrote: > As the Linux kernel, unconditionally, builds the dtc application and > it is the compatible version with the DeviceTree files shipped within > the kernel it is better to use it and the kernel build system to > generate the dtb files. > > Some DeviceTree files rely on CPP and kernel headers to be able to > generate the dtb binary contents and it is harder to replicate it > outside of Linux kernel build system so we /use/ it. > > To comply with these assumptions we need to use the dtb file when > calling 'make' instead of pointing to the DeviceTree source file; the > code has been made backward compatible but it is advised to move to > the new definition to avoid warnings as: > > ,----[ Original definition ] > | KERNEL_DEVICETREE =3D "${S}/arch/arm/boot/dts/imx6q-sabresd.dts" > `---- > > Becomes: > > ,----[ New definition ] > | KERNEL_DEVICETREE =3D "imx6q-sabresd.dtb" > `---- I currently have a "bbappend" that adds a DTB file from outside the=20 kernel (listing driver configuration that is implemented in the FPGA=20 part of the SOC). The DTB file /include/s files from the kernel (that=20 is, it gets everything from the standard files and adds a single device). How would I go about adding this after this change? (as for the change itself, I'm all in favor) Mike. Met vriendelijke groet / kind regards, Mike Looijmans TOPIC Embedded Systems Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best Telefoon: (+31) =E2=80=93 (0)499 - 33.69.79 Telefax: (+31) - (0)499 - 33.69.70 E-mail: mike.looijmans@topic.nl Website: www.topic.nl Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluit= end bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht = en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan.= Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwi= jl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde= te ontvangen, wordt u verzocht de afzender hierover direct te informeren e= n het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de i= nhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door= een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de event= ueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPI= C Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeien= d uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij beh= orende bijlagen. The contents of this message, as well as any enclosures, are addressed pers= onally to, and thus solely intended for the addressee. They may contain inf= ormation regarding a third party. A recipient who is neither the addressee,= nor empowered to receive this message on behalf of the addressee, is kindl= y requested to immediately inform the sender of receipt, and to destroy the= message and the enclosures. Any use of the contents of this message and/or= the enclosures by any other person than the addressee or person who is emp= owered to receive this message, is illegal towards the sender and/or the af= orementioned third party. TOPIC Embedded Systems is not liable for any dam= age as a result of the use and/or acceptance of this message and as well as= any enclosures.