All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Tom Rini <trini@konsulko.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	 U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: External dts building
Date: Thu, 14 Oct 2021 12:24:37 -0600	[thread overview]
Message-ID: <CAPnjgZ3MOBx_0nfaRTGGcJWons3BZjD0TjwWAaq6NwKncM5OGg@mail.gmail.com> (raw)
In-Reply-To: <20211014134548.GB7964@bill-the-cat>

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' ?

Regards,
Simon

  parent reply	other threads:[~2021-10-14 18:24 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 [this message]
2021-10-14 19:23     ` Giulio Benetti
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=CAPnjgZ3MOBx_0nfaRTGGcJWons3BZjD0TjwWAaq6NwKncM5OGg@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=giulio.benetti@benettiengineering.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.