public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RESEND 2/2] cmd: fdt: add fdt overlay application subcommand
Date: Tue, 10 May 2016 13:45:00 +0200	[thread overview]
Message-ID: <20160510114500.GJ3733@lukather> (raw)
In-Reply-To: <CAPnjgZ3M3MwrCNUM-83n+mPmmjwUXHXqAg8rH=OMAT8xYvN7+w@mail.gmail.com>

Hi Simon,

I'm finally taking the time to address the reviews that have been made
here.

On Sat, Apr 09, 2016 at 12:40:14PM -0600, Simon Glass wrote:
> Hi Maxime,
> 
> On 4 April 2016 at 12:25, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > The device tree overlays are a good way to deal with user-modifyable
> > boards or boards with some kind of an expansion mechanism where we can
> > easily plug new board in (like the BBB or the raspberry pi).
> >
> > However, so far, the usual mechanism to deal with it was to have in Linux
> > some driver detecting the expansion boards plugged in and then request
> > these overlays using the firmware interface.
> >
> > That works in most cases, but in some cases, you might want to have the
> > overlays applied before the userspace comes in. Either because the new
> > board requires some kind of an early initialization, or because your root
> > filesystem is accessed through that expansion board.
> >
> > The easiest solution in such a case is to simply have the component before
> > Linux applying that overlay, removing all these drawbacks.
> >
> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> > ---
> >  cmd/Makefile          |   2 +-
> >  cmd/fdt.c             |  19 +++
> >  cmd/fdt_overlay.c     | 464 ++++++++++++++++++++++++++++++++++++++++++++++++++
> >  include/fdt_support.h |   2 +-
> >  4 files changed, 485 insertions(+), 2 deletions(-)
> >  create mode 100644 cmd/fdt_overlay.c
> 
> I'm happy to take this into the U-Boot tree while you try to get it
> applied upstream, but please confirm that you will do this and by
> when. I suggest you sent an email referring to this patch.
> 
> Also fdt_overlay.c should go in lib/libfdt/. If this functionality is
> rejected for libfdt (as was fdtgrep) then we'll move it to lib/.

I'm definitely ok to send it to libfdt if that's what you meant by
upstream. I'll push it at the same time I'm pushing the next version
of these patches, just to make sure we progress as fast as we can on
this.

> Finally, please take a look at adding a test for this, with some
> sample files. See test/py.

However, that will be a bit difficult. In order to be used, the DT
overlays require the overlay support in dtc, which is still not
included upstream. So the majority of the users of U-Boot won't have
that support, meaning that these tests will likely fail for them (even
though the code might be correct), resulting in a lot of false
negative.

How do you want me to proceed?

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160510/7ec34018/attachment.sig>

  reply	other threads:[~2016-05-10 11:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 18:25 [U-Boot] [PATCH RESEND 0/2] cmd: fdt: Add device tree overlays support Maxime Ripard
2016-04-04 18:25 ` [U-Boot] [PATCH RESEND 1/2] cmd: fdt: Narrow the check for fdt addr Maxime Ripard
2016-04-09 18:36   ` Simon Glass
2016-04-04 18:25 ` [U-Boot] [PATCH RESEND 2/2] cmd: fdt: add fdt overlay application subcommand Maxime Ripard
2016-04-05 22:03   ` Pantelis Antoniou
2016-04-08 21:29     ` Rob Herring
2016-04-13 19:42       ` Tom Rini
2016-04-13 19:50         ` Pantelis Antoniou
2016-04-09 18:40   ` Simon Glass
2016-05-10 11:45     ` Maxime Ripard [this message]
2016-05-19  4:00       ` Simon Glass
2016-05-19  6:54       ` Pantelis Antoniou
2016-05-01 18:55   ` Simon Glass
2016-05-02 11:10     ` Maxime Ripard

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=20160510114500.GJ3733@lukather \
    --to=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox