linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Icenowy Zheng <icenowy@aosc.io>
To: Maxime Ripard <maxime@cerno.tech>
Cc: devicetree@vger.kernel.org,
	Jernej Skrabec <jernej.skrabec@siol.net>,
	Samuel Holland <samuel@sholland.org>,
	linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
	Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-sunxi] Re: [PATCH 3/3] arm64: allwinner: dts: a64: add DT for PineTab developer sample
Date: Sat, 28 Nov 2020 19:28:19 +0800	[thread overview]
Message-ID: <1666a61f6ea3e7d573795f9000a0b096c7b7dee0.camel@aosc.io> (raw)
In-Reply-To: <20201128103827.d6sfc2eumli2betx@gilmour>

在 2020-11-28星期六的 11:38 +0100，Maxime Ripard写道：
> On Mon, Nov 23, 2020 at 09:10:38PM +0800, Icenowy Zheng wrote:
> > > > > > > Okay. But I'm not satisfied with a non-public sample
> > > > > > > occupies
> > > > > > > the pinetab name. Is rename it to pinetab-dev and add a
> > > > > > > pinetab-retail okay?
> > > > > > 
> > > > > > To me, naming the production version anything but "pinetab"
> > > > > > isn't
> > > > > > satisfying either.
> > > > > 
> > > > > I understand where you're coming from, but the point I was
> > > > > making my
> > > > > previous mail is precisely that it's not really possible.
> > > > > 
> > > > > You want to name the early adopter version _the_ production
> > > > > version. Let's assume the hardware changes again between the
> > > > > early
> > > > > adopter and mass-production version. Which one will be _the_
> > > > > production version? The early-adopter or the mass-produced
> > > > > one?
> > > > > 
> > > > > There's really no good answer here, and both would suck in
> > > > > their
> > > > > own way. The only way to deal with this is to simply avoid
> > > > > defining one version as the one true board, and just loading
> > > > > the
> > > > > proper DT in u-boot based on whatever clue we have of the
> > > > > hardware
> > > > > revision.
> > > > Then will it be okay to rename current pinetab DT to
> > > > pinetab-sample and then introduce new DTs all with suffixes?
> > > 
> > > No. From my previous mail:
> > 
> > It can be seen as dropping the PineTab DT and introduce new DTs
> > with
> > suffix.
> > 
> > Do we have rule that we cannot drop boards?
> 
> Are you really arguing that removing a DT and then adding an
> identical
> one under a different name is not renaming it?

Then we can just keep confusing name?

If we do so, how can we mark the new DT as "the user should use this
one"?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-28 11:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07 12:49 [PATCH 0/3] Switch PineTab DT LCD panel to retail one Icenowy Zheng
2020-11-07 12:50 ` [PATCH 1/3] arm64: allwinner: dts: a64: pinetab: switch LCD panel to production one Icenowy Zheng
2020-11-07 12:52 ` [PATCH 2/3] dt-bindings: arm: sunxi: add PineTab developer sample DT binding Icenowy Zheng
2020-11-09 22:02   ` Rob Herring
2020-11-07 12:53 ` [PATCH 3/3] arm64: allwinner: dts: a64: add DT for PineTab developer sample Icenowy Zheng
2020-11-10 10:39   ` Maxime Ripard
2020-11-10 10:41     ` Icenowy Zheng
2020-11-16 15:55       ` Maxime Ripard
2020-11-16 18:36         ` [linux-sunxi] " Icenowy Zheng
2020-11-20 15:59           ` Maxime Ripard
2020-11-20 23:30             ` Icenowy Zheng
2020-11-21  2:51               ` Samuel Holland
2020-11-23 11:15                 ` Maxime Ripard
2020-11-23 11:25                   ` Icenowy Zheng
2020-11-23 12:53                     ` Maxime Ripard
2020-11-23 13:10                       ` Icenowy Zheng
2020-11-28 10:38                         ` Maxime Ripard
2020-11-28 11:28                           ` Icenowy Zheng [this message]
2020-11-28 11:54                             ` Clément Péron
2020-11-28 11:59                               ` Icenowy Zheng
2020-11-28 21:07                                 ` Clément Péron
2020-12-01 10:35                                   ` Maxime Ripard
2020-12-06 21:03                                     ` Clément Péron
2020-12-07 10:07                                       ` Maxime Ripard

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=1666a61f6ea3e7d573795f9000a0b096c7b7dee0.camel@aosc.io \
    --to=icenowy@aosc.io \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@siol.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime@cerno.tech \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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).