public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 09/10] kconfig: move CONFIG_OF_* to Kconfig
Date: Fri, 26 Sep 2014 09:49:01 -0400	[thread overview]
Message-ID: <20140926134901.GS25506@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ35Q4BAVnPJTrAutEtnkHvQQV5hXq3+KdoJ0Fr_e3roSA@mail.gmail.com>

On Thu, Sep 25, 2014 at 07:44:30AM -0600, Simon Glass wrote:
> Hi,
> 
> On 25 September 2014 07:18, Tom Rini <trini@ti.com> wrote:
> > On Thu, Sep 25, 2014 at 04:38:09PM +0900, Masahiro Yamada wrote:
> >> Hi Simon,
> >>
> >>
> >>
> >> On Wed, 24 Sep 2014 17:08:11 -0600
> >> Simon Glass <sjg@chromium.org> wrote:
> >>
> >> > > +config OF_EMBED
> >> > > +       bool "Embedded DTB for DT control"
> >> > > +       help
> >> > > +         If this option is enabled, the device tree will be picked up and
> >> > > +         built into the U-Boot image.
> >> >
> >> > Can you please add " This is suitable for debugging
> >> > and development only and is not recommended for production devices."
> >>
> >>
> >> Why is CONFIG_OF_EMBED not recommended for production devices?
> >
> > It's kind-of a question for the devicetree folks.  The last time (a
> > while back now) I asked for some general advice on how a DT should be
> > shipped with hardware, being able to update the DT without replacing the
> > whole of firmware was seen as a good thing.  Combine this with that we
> > should try (yes, we can't today due to incompatible bindings) share the
> > DT between U-Boot and the kernel (or really, U-Boot and anything but
> > again, last I checked the BSD bindings were very very different),
> > embedding doesn't seem good.
> 
> Addressing the binding differences, it's hard to see what these are
> right now since the sorting and other churn in the Linux device tree
> files. I think it would be good to sync the U-Boot files to the Linux
> ones so we can see what bindings still differ.

Yes, agreed.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140926/015e1d0c/attachment.pgp>

  reply	other threads:[~2014-09-26 13:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 10:59 [U-Boot] [PATCH v3 09/10] kconfig: move CONFIG_OF_* to Kconfig Masahiro Yamada
2014-09-22 10:59 ` [U-Boot] [PATCH v3 10/10] kconfig: move CONFIG_DEFAULT_DEVICE_TREE to kconfig Masahiro Yamada
2014-09-24 23:09   ` Simon Glass
2014-09-25  8:06     ` Masahiro Yamada
2014-09-25 13:49       ` Simon Glass
2014-09-25 14:46   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-09-24 23:08 ` [U-Boot] [PATCH v3 09/10] kconfig: move CONFIG_OF_* to Kconfig Simon Glass
2014-09-25  7:12   ` Michal Simek
2014-09-25  7:38   ` Masahiro Yamada
2014-09-25 13:18     ` Tom Rini
2014-09-25 13:44       ` Simon Glass
2014-09-26 13:49         ` Tom Rini [this message]
2014-09-26 14:52           ` Stephen Warren
2014-09-26 15:24             ` Tom Rini
2014-09-26 15:35               ` Stephen Warren
2014-09-26 18:33               ` Simon Glass
2014-10-02 13:09           ` Masahiro Yamada
2014-10-04  2:20             ` Simon Glass
2014-09-25 14:46 ` [U-Boot] [U-Boot, v3, " Tom Rini

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=20140926134901.GS25506@bill-the-cat \
    --to=trini@ti.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