mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: real pedantic whining: "devicetree" isn't really a single word
Date: Thu, 3 Jul 2014 07:40:46 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407030738001.21622@localhost> (raw)
In-Reply-To: <20140703064504.GN14257@pengutronix.de>

On Thu, 3 Jul 2014, Sascha Hauer wrote:

> On Wed, Jul 02, 2014 at 10:12:33PM +0200, Holger Schurig wrote:
> > Oh, please bear with us germans, indians, italians and whoever we are
> > with our limited pidgin-english knowledge.
> >
> > No, to turn it the other way around: it's great that a native-english
> > speaker with knowledge and taste of the language goes over the
> > documentation.
> >
> > And at least it's now called "device tree", and no longer just "of"
> > (from open firmware) :-)
>
> Yeah, naming functions of_* is one thing, but writing of in text
> looks just ugly and confusing. Writing OF is only slightly better.
> Speaking of "device tree" is surely better, but unfortunately this is such
> a generic term. What else do we have?
>
> - Flat Device Tree (FDT), describes the binary format
> - Device Tree Blob (DTB), same as FDT
> - Device Tree Source (DTS)
>
> There's just no good name for this mechanism.

  yes, i've been down this road before, it's messy. the only thing i
think would be worth changing is to simply not use "devicetree" as if
it was a single word -- all of the docs i've seen for device trees
always treats that as two words. but that's not high on my priority
list ... we can revisit it down the road if anyone thinks it's worth
it. moving on ...

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

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

      reply	other threads:[~2014-07-03 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 19:01 Robert P. J. Day
2014-07-02 20:12 ` Holger Schurig
2014-07-03  6:45   ` Sascha Hauer
2014-07-03 11:40     ` Robert P. J. Day [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=alpine.LFD.2.11.1407030738001.21622@localhost \
    --to=rpjday@crashcourse.ca \
    --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