mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Barbier, Renaud" <renaud.barbier@abaco.com>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: DTB overlay
Date: Wed, 20 May 2020 08:12:31 +0000	[thread overview]
Message-ID: <MN2PR16MB313584995C3AD470E497AC1691B60@MN2PR16MB3135.namprd16.prod.outlook.com> (raw)
In-Reply-To: <MN2PR16MB3135D515C95492ACE382152F91B90@MN2PR16MB3135.namprd16.prod.outlook.com>

Forgot to mention, I am using v2020.03.

I will see if any newer code fix this error message issue

> -----Original Message-----
> From: barebox [mailto:barebox-bounces@lists.infradead.org] On Behalf Of
> Barbier, Renaud
> Sent: 19 May 2020 18:34
> To: barebox@lists.infradead.org
> Subject: DTB overlay
> 
> 
> 
> [**EXTERNAL SOURCE**]:Please verify the source before clicking link or
> opening attachment.
> 
> Is there a limit on the number of overlay that can be  loaded with the
> of_overlay command?
> 
> It does not complain if I load two overlays. However, when booting my FIT
> image, I get twice the message:
> of_overlay: failed to copy symbols from overlay
> 
> Still all node modifications are added to the base device tree.
> 
> The error message is not displayed if I add only one overlay.
> 
> 
> 
> 
> 
> Cheers,
> Renaud
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-05-20  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 17:33 Barbier, Renaud
2020-05-20  8:12 ` Barbier, Renaud [this message]
2020-05-20  9:58 ` Sascha Hauer

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=MN2PR16MB313584995C3AD470E497AC1691B60@MN2PR16MB3135.namprd16.prod.outlook.com \
    --to=renaud.barbier@abaco.com \
    --cc=barebox@lists.infradead.org \
    /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