u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: External dts building
Date: Thu, 14 Oct 2021 21:23:16 +0200	[thread overview]
Message-ID: <7675B66B-B9D2-4BDE-AB7F-9625B4203EFF@benettiengineering.com> (raw)
In-Reply-To: <CAPnjgZ3MOBx_0nfaRTGGcJWons3BZjD0TjwWAaq6NwKncM5OGg@mail.gmail.com>

Hi Simon,

> Il giorno 14 ott 2021, alle ore 20:24, Simon Glass <sjg@chromium.org> ha scritto:
> 
> Hi,
> 
>> On Thu, 14 Oct 2021 at 07:46, Tom Rini <trini@konsulko.com> wrote:
>> 
>>> On Thu, Oct 14, 2021 at 02:53:30AM +0200, Giulio Benetti wrote:
>>> 
>>> Hello All,
>>> 
>>> is there a way to pass a dts file without touching the arch/arm/boot/dts/Makefile?
>>> 
>>> On Buildroot we support the possibility to pass an external dts by copying it to the uboot sources to
>>> be built but since uboot version 2020.01 it doesn’t work anymore.
>>> 
>>> So I’ve proposed a patch to prepend the dts file in the Makefile above, but this has drawbacks, like we reconfigure(it keeps adding files every time).
>>> 
>>> So I ask you, is there a more canonical way already to achieve this?
>> 
>> Not exactly, and it's something we're very much actively discussing
>> right now.
> 
> Are you using 'make DEVICE_TREE=xxx' ?

Yes but it doesn’t work if you don’t add an entry into arch/arm/dts/Makefile
Before version 2020.01 worked, but not after it.

Best regards
Giulio

> 
> Regards,
> Simon


  reply	other threads:[~2021-10-14 19:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  0:53 External dts building Giulio Benetti
2021-10-14 13:45 ` Tom Rini
2021-10-14 18:08   ` Giulio Benetti
2021-10-14 18:22     ` Tom Rini
2021-10-14 21:27       ` Giulio Benetti
2021-10-14 18:24   ` Simon Glass
2021-10-14 19:23     ` Giulio Benetti [this message]
2021-10-14 20:43       ` Simon Glass
2021-10-14 21:12         ` Giulio Benetti
2021-10-15  0:53           ` Simon Glass
2021-10-15  3:06             ` Giulio Benetti
2021-10-16  0:31               ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7675B66B-B9D2-4BDE-AB7F-9625B4203EFF@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).