linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: robh+dt@kernel.org, stephen.boyd@linaro.org, broonie@kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	mark.rutland@arm.com, Matt Porter <mporter@konsulko.com>,
	koen@dominion.thruhere.net, linux@roeck-us.net, marex@denx.de,
	wsa@the-dreams.de, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual
Date: Fri, 8 Jul 2016 12:20:11 -0700	[thread overview]
Message-ID: <577FFCEB.9010600@gmail.com> (raw)
In-Reply-To: <2D8CFA9A-C317-4C02-9893-169B4B77E01E@konsulko.com>

On 07/08/16 00:26, Pantelis Antoniou wrote:
> Hi David,
> 
>> On Jul 7, 2016, at 10:15 , David Gibson <david@gibson.dropbear.id.au> wrote:
>>

< snip >

>> Given that we're going to need new code to support this new connector
>> model, I think we should also fix some of the uglies in the current
>> overlay format while we're at it.
>>
> 
> We need to keep compatibility with the old format. There are 5 million
> RPIs sold, half a million beaglebones and C.H.I.P. is coming out too.
> They all use overlays in one form or another.
> 
> That’s not counting all the custom boards that actively use them.
> 
> We have a user base now.

Please not that I AM NOT suggesting the we remove compatibility with
the old format!!!

But I need to push back on the idea that we have a user base that we
need to keep compatibility with.  If I understand correctly, that
user base is based on using much code that is not in mainline, including
an altered dtc and a cape manager.

People using out of tree code can not use the fact that code exists and
is being widely used to force us to mainline that out of tree code.
That is the risk of using out of tree code.

I do not want to start a big discussion about this now since there is
no plan to remove the compatibility at this point.

-Frank

  parent reply	other threads:[~2016-07-08 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02 23:55 [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual frowand.list
2016-07-02 23:55 ` [RFC PATCH 1/1] device tree connectors, using plugs and sockets frowand.list
2016-07-03  6:06 ` [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand
2016-07-04 15:22 ` Mark Brown
2016-07-04 18:15   ` Frank Rowand
2016-07-05 18:01 ` Pantelis Antoniou
2016-07-06 17:40   ` Frank Rowand
2016-07-07  7:15 ` David Gibson
2016-07-08  7:26   ` Pantelis Antoniou
2016-07-08  7:43     ` David Gibson
2016-07-08 19:20     ` Frank Rowand [this message]
2016-07-08 19:25       ` Frank Rowand
2016-07-08 19:22   ` Frank Rowand

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=577FFCEB.9010600@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=broonie@kernel.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marex@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=mporter@konsulko.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.org \
    --cc=stephen.boyd@linaro.org \
    --cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).