From: David Gibson <david@gibson.dropbear.id.au>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Tom Rini <trini@ti.com>, Stephen Warren <swarren@wwwdotorg.org>,
cross-distro@lists.linaro.org,
Mark Rutland <Mark.Rutland@arm.com>,
devicetree@vger.kernel.org, Tom Rini <tom.rini@gmail.com>,
Ian Campbell <ian.campbell@citrix.com>,
Arnd Bergmann <arnd@arndb.de>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>
Subject: Re: [RFC] Best practices for hardware shipping device trees
Date: Mon, 19 Aug 2013 10:15:14 +1000 [thread overview]
Message-ID: <20130819001514.GA9098@voom.fritz.box> (raw)
In-Reply-To: <alpine.LFD.2.03.1308152241410.14472@syhkavp.arg>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
On Thu, Aug 15, 2013 at 10:51:18PM -0400, Nicolas Pitre wrote:
> On Fri, 16 Aug 2013, David Gibson wrote:
>
> > On Wed, Aug 14, 2013 at 10:57:36PM -0400, Nicolas Pitre wrote:
> > > On Wed, 14 Aug 2013, Tom Rini wrote:
> > > > On 08/14/2013 08:37 PM, Nicolas Pitre wrote:
> > > > > On Wed, 14 Aug 2013, Tom Rini wrote:
> > [snip]
> > > Well, the hard guideline should require that the DTB be updateable and
> > > not linked with nor generated by the bootloader or firmware. That
> > > implies some storage separate from the bootloader but this doesn't need
> > > to be a filesystem.
> >
> > Wait, what!?
> >
> > Much as I think a bunch of the current problems have been caused by
> > being overly keen to push the dtb into firmware, we shouldn't *ban*
> > the original Open Firmware model of the device tree, where it is
> > generated by the firmware and consumed by the OS.
>
> If the DTB generating firmware can be updated by the end user just as
> easily and safely as a standalone DTB then that's probably fine. But we
> do know that many people/organizations are not willing to let end users
> upgrade bootloaders due to the risks associated with such an operation.
> So in that case we may not suggest the DTB be tied to the
> bootloader/firmware.
No, even then. I really don't think trying to ban the actual,
original Open Firmware model of device tree usage is sensible.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-19 1:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 15:13 [RFC] Best practices for hardware shipping device trees Tom Rini
2013-08-14 16:38 ` Jason Cooper
2013-08-14 18:41 ` Tom Rini
2013-08-14 18:53 ` Jason Cooper
2013-08-14 16:44 ` Stephen Warren
2013-08-14 17:20 ` Jason Cooper
2013-08-14 18:25 ` Tom Rini
2013-08-15 0:37 ` Nicolas Pitre
2013-08-15 2:09 ` Tom Rini
2013-08-15 2:57 ` Nicolas Pitre
2013-08-15 14:53 ` Tom Rini
2013-08-15 15:30 ` Stephen Warren
2013-08-15 16:37 ` Tom Rini
2013-08-15 17:31 ` Stephen Warren
2013-08-15 18:56 ` Tom Rini
2013-08-15 22:34 ` Stephen Warren
2013-08-15 15:45 ` Nicolas Pitre
2013-08-15 17:00 ` Tom Rini
2013-08-15 23:59 ` David Gibson
2013-08-16 2:51 ` Nicolas Pitre
2013-08-19 0:15 ` David Gibson [this message]
2013-08-19 18:43 ` Nicolas Pitre
2013-08-20 6:40 ` Alexander Graf
2013-08-20 12:02 ` Nicolas Pitre
2013-08-20 17:02 ` Matt Sealey
2013-08-20 17:29 ` Nicolas Pitre
2013-08-20 15:03 ` 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=20130819001514.GA9098@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=Mark.Rutland@arm.com \
--cc=arnd@arndb.de \
--cc=cross-distro@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=nicolas.pitre@linaro.org \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tom.rini@gmail.com \
--cc=trini@ti.com \
/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.