devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve McIntyre <steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Francois Ozog <francois.ozog-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: Device Tree Evolution Project - call notes - 12th February
Date: Wed, 19 Feb 2020 17:53:29 +0000	[thread overview]
Message-ID: <20200219175329.GD7618@linaro.org> (raw)
In-Reply-To: <CAHFG_=VNst-6+rG8gHet8LwcE0H37YXvqMub71eqcoPu3_d7Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Francois!

On Thu, Feb 13, 2020 at 04:23:35PM +0100, Francois Ozog wrote:
>On Thu, 13 Feb 2020 at 15:51, Steve McIntyre <steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:

...

>>       26. AB: When discussed moving years ago - discussed to put in
>>           separate directories out of tree. As long as still plan on
>>           moving them out. Don’t want to move them twice. If around
>>           the same time would do them together. First want to get
>>           agreement on overlays. Takes half a year. how many files?
>>       27. BM: think github is fairly complete or at least a good
>>           estimate. Covers only the boards we actively support.
>>       28. AB: RPi tree has around 300 overlays.
>>       29. RH: For TI is 12.
>>       30. BM: Beaglebone capes are not overlays. If a customer of TI
>>           invents own overlays - vendor should be “Customer X”, not
>>           TI. Is that aligned with your thinking?
>If we take the "responsibility" out of the picture, I would have
>thought those are overlays. Or shall we name them something like
>"composable DTBs" ?

Sorry, I'm not following you here. Maybe the notes aren't clear
enough, and my addled brain is struggling to remember exactly what was
said here. :-/

Cheers,
-- 
Steve McIntyre                                steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs


  parent reply	other threads:[~2020-02-19 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 14:50 Device Tree Evolution Project - call notes - 12th February Steve McIntyre
     [not found] ` <20200213145028.GR3697-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2020-02-13 15:23   ` Francois Ozog
     [not found]     ` <CAHFG_=VNst-6+rG8gHet8LwcE0H37YXvqMub71eqcoPu3_d7Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-19 17:53       ` Steve McIntyre [this message]
2020-02-13 17:24   ` Frank Rowand
     [not found]     ` <cfbcee96-ac90-c482-1a36-b803d3e9ce2d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-02-13 20:57       ` Frank Rowand
2020-02-19 18:05       ` Steve McIntyre
     [not found]         ` <20200219180534.GE7618-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2020-02-19 18:26           ` Frank Rowand
     [not found]             ` <6391cf01-ebf0-fcb7-9c86-679d335c16d2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-02-20 11:32               ` Steve McIntyre
2020-02-19 18:07   ` Steve McIntyre

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=20200219175329.GD7618@linaro.org \
    --to=steve.mcintyre-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=francois.ozog-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).