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: Mon, 2 May 2016 13:10:24 +0200 [thread overview]
Message-ID: <20160502111024.GQ17159@lukather> (raw)
In-Reply-To: <CAPnjgZ32V4dStThWevZ_NCjbBAN4qrdBbOkxmnvxBc-dwAkygQ@mail.gmail.com>
Hi Simon,
On Sun, May 01, 2016 at 12:55:07PM -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>
>
> Will there be a new version of this patch?
Yeah, sorry, I haven't had the time to address all the comments you
made, but there will definitely be a second version addressing the
comments Pantelis, Rob, Stefan and you made.
Probably not before a couple of weeks though :/
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/20160502/2fa9c09f/attachment.sig>
prev parent reply other threads:[~2016-05-02 11:10 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
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 [this message]
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=20160502111024.GQ17159@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 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.