Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add out-of-source U-Boot device tree support
Date: Tue, 28 Mar 2017 21:53:34 +0200	[thread overview]
Message-ID: <20170328215334.405952d9@free-electrons.com> (raw)
In-Reply-To: <54cae0a0-a7a5-9ef0-08c8-a14e871cf8bb@mind.be>

Hello,

On Tue, 28 Mar 2017 11:01:46 +0200, Arnout Vandecappelle wrote:

> > Have reconsidered this suggestion. I think that perhaps it would be best
> > not to make the U-boot option dependent on the Linux option. As Linux
> > and U-Boot use two different device tree sources, there may be occasions
> > when custom DTS configuration must be made to one or the other rather
> > than both. This is the case with my boards, which have device tree
> > support in Linux, but not in U-Boot.  
> 
>  Certainly, but I only suggested to *default* to the same DTS. It is also
> possible that the kernel isn't built at all by Buildroot, or that it uses an
> in-tree DTS, or that it is built without DTS because the DTB is provided by
> U-Boot. All of these cases are covered by the "if
> BR2_LINUX_KERNEL_USE_CUSTOM_DTS" part. And even if the both kernel and U-Boot
> use a DTS, it is possible to change the default.

I am not entirely convinced that this:

  default BR2_LINUX_KERNEL_CUSTOM_DTS_PATH if BR2_LINUX_KERNEL_USE_CUSTOM_DTS

is really a good idea. IMO, it tries to be too "clever". I'd really
prefer to keep the U-Boot and Linux configurations independent from
each other.



Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-28 19:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  6:12 [Buildroot] [PATCH] Add out-of-source U-Boot device tree support James Balean
2017-03-27 12:12 ` Arnout Vandecappelle
2017-03-28  1:19   ` James Balean
2017-03-28  6:14   ` James Balean
2017-03-28  9:01     ` Arnout Vandecappelle
2017-03-28 19:53       ` Thomas Petazzoni [this message]
2017-03-28 20:19         ` Arnout Vandecappelle
2017-03-28 20:29           ` Thomas Petazzoni
2017-03-28 22:17             ` Arnout Vandecappelle
2017-03-29  7:09               ` Thomas Petazzoni
2017-04-05  3:29                 ` James Balean
2017-04-05  3:45                   ` [Buildroot] [PATCH v2] " James Balean
2017-04-05 20:30                     ` Thomas Petazzoni

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=20170328215334.405952d9@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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