All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Balean <james@balean.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add out-of-source U-Boot device tree support
Date: Tue,  4 Apr 2017 22:29:50 -0500	[thread overview]
Message-ID: <1491362990-3697-1-git-send-email-james@balean.com.au> (raw)
In-Reply-To: <20170329090909.4c74c734@free-electrons.com>

Hi All,

Thank you for your responses. I will submit a new version of the patch
with your suggestions following this.

On 29 March 2017 at 18:09, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> > > Not necessarily. The DT can be used by U-Boot itself to know which
> > > peripherals are available, and how they should be configured.  
> > 
> >  But U-Boot can always pass the device tree it uses internally to
> >  the kernel, no?
> 
> I don't know. Would have to check.

I believe it is possible to use U-Boot's device tree blob when booting
Linux. U-Boot's DTB is simply concatenated on the end of itself, so the
address at which the blob starts could be determined and supplied to the
'bootm' command when booting Linux. I have not tested this though, so
will report back if I get around to it.

Thanks again,
James

  reply	other threads:[~2017-04-05  3:29 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
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 [this message]
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=1491362990-3697-1-git-send-email-james@balean.com.au \
    --to=james@balean.com.au \
    --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 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.