mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	barebox@lists.infradead.org, devicetree@vger.kernel.org,
	Ian Campbell <ijc@hellion.org.uk>
Subject: Re: Devicetree Maintenance in barebox
Date: Sun, 09 Feb 2014 11:58:06 -0600	[thread overview]
Message-ID: <E1WCYdq-0004eu-Gr@jdl.com> (raw)
In-Reply-To: <20140207141028.GT8533@titan.lakedaemon.net>

> Hi Sascha,
> 
> + Grant Likely, Ian Campbell, devicetree ML
> 
> Also, In the DT meeting earlier this week, Grant Likely said he has the
> request in to create a separate mailinglist for collaboration between
> the different devicetree users (BSD, Linux, etc).

...

> I think the proper solution will percolate out of the first
> cross-project discussions on the new ML.

...

> Definitely fodder for the new ML.
> 
> Grant, can you please add Sascha to the list of folks to notify when
> the new ML is ready?

I don't think there needs to be a different mailing list
in order to combine or discuss other OS's use of the device
tree compiler.  The  DTC is OS and Use-agnostic.  Discussions
of DTC needs for FreeBSD can happen right here as the orginal
purpose of this list was DTC discussion.

Are you, and Grant(?), suggesting that a separate list
should be created for FreeBSD use of DTS-file contents?
Or that DTS-file-content related discussions should be
separated from DTC discussions?


> imho, the goal is to not have any project tied to a specific version
> of the devicetree.
>
> iow, we don't break backwards compatibility in the
> devicetrees, and projects should revert to default behavior if new dt
> parameters are missing.  This means Linux and BSD shouldn't need to keep
> a current copy of the devicetree in their trees.  However, building the
> bootloader is a different animal.  It needs to provide the dt blob...

The devicetree source file format hasn't changed in years.
Yes, it is enhanced, but compatibly.  Or do you mean the
contents of the DTB for some specific platform?

Thanks,
jdl

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

  parent reply	other threads:[~2014-02-09 17:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  7:13 Sascha Hauer
2014-02-07  7:39 ` Alexander Shiyan
2014-02-07  8:47   ` Sascha Hauer
2014-02-07  9:01     ` Alexander Shiyan
2014-02-07  7:49 ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-07 14:10 ` Jason Cooper
2014-02-07 17:51   ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-09 17:58   ` Jon Loeliger [this message]
2014-02-10 11:35     ` Ian Campbell
2014-02-10 15:06     ` Jason Cooper
2014-02-10 11:38   ` Ian Campbell
2014-02-17 19:42 ` Jason Cooper

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=E1WCYdq-0004eu-Gr@jdl.com \
    --to=jdl@jdl.com \
    --cc=barebox@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=ijc@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    /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