mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "'barebox@lists.infradead.org'" <barebox@lists.infradead.org>,
	"Dgien, David [US] (MS)" <David.Dgien@ngc.com>
Subject: Re: Barebox device tree overlay support
Date: Fri, 12 Jan 2018 11:11:32 +0100	[thread overview]
Message-ID: <20180112101132.ebgz3aqj5scahe5a@flea.lan> (raw)
In-Reply-To: <20180112074226.s7dyuvovw3t6y3t7@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]

Hi,

On Fri, Jan 12, 2018 at 08:42:26AM +0100, Sascha Hauer wrote:
> On Thu, Jan 11, 2018 at 03:40:49PM +0000, Dgien, David [US] (MS) wrote:
> > Hello,
> > 
> > When going through the archives it looks like a set of patches
> > were submitted to support device tree overlays in barebox in
> > http://lists.infradead.org/pipermail/barebox/2015-March/022674.html.
> > But they weren't accepted because overlays weren't fully
> > implemented in the DTC yet.
> > 
> > It looks like overlay support was mainlined in the kernel in
> > 4.11. ( kernel/git/torvalds/linux.git:
> > be5165a51d2500ae1afa1236a8b09858831fdf7e )
> 
> I am still not sure which parts got merged and which are still pending.
> There are still overlay patches floating around.

The only thing that's missing in the kernel at the moment is a
user-space interface to load overlays, but the rest has been there for
quite some time.

> > Would it be possible to take another look at pulling these patches
> > into the barebox mainline?
> 
> Generally yes. If you like, please rebase test and respin the patches.

The libfdt gained support to apply overlays quite some time ago
already, so this should be as easy as updating it to a recent enough
version, and creating a wrapper around fdt_apply. This is what U-Boot
is doing.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

  reply	other threads:[~2018-01-12 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 15:40 Dgien, David [US] (MS)
2018-01-12  7:42 ` Sascha Hauer
2018-01-12 10:11   ` Maxime Ripard [this message]
2018-01-12 10:14     ` 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=20180112101132.ebgz3aqj5scahe5a@flea.lan \
    --to=maxime.ripard@free-electrons.com \
    --cc=David.Dgien@ngc.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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