linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1
Date: Tue, 6 Sep 2016 15:40:51 +0530	[thread overview]
Message-ID: <84be68f4-c5a6-0afe-c402-1adba9172918@ti.com> (raw)
In-Reply-To: <CAOCHtYiFjB-cuABmCiw96spc-De+qNNQYGrjp-MmNDuH2mJ9Bw@mail.gmail.com>

On Friday 02 September 2016 07:22 PM, Robert Nelson wrote:
> On Fri, Sep 2, 2016 at 5:41 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>> + Robert Nelson
>>
>> On Friday 02 September 2016 02:36 PM, Nishanth Menon wrote:
>>
>> I understand that there are existing users of A2 boards and so we simply
>> cannot remove support for those boards (at least yet).
>>
>> But given the small numbers of A2 boards, its also quite likely that we
>> will not have enough test coverage for those boards. Especially as years
>> pass and there are fewer and fewer people with access to working A2 boards.
> 
> I have a A1, A2 and a B1, that i use for testing for
> beagleboard.org...  The A1 use to be ssh-accessible for developers,
> but since moving to my new house, I haven't "yet" got that one setup
> for developers.  Right now i'm using the A2 & B1 for development of
> our default images.
> 
> Jason Kridner also has a number of boards

Availability of hardware _somewhere_ is one aspect. I am still worried
about the big difference in scale. A2 are ~200 in number where as the
production version should be in thousands.

Reuse is meant to reduce maintenance cost. In this case though, it seems
like it will do exactly the opposite - making anyone with a production
version rely on few with a non-production version to make any updates at
all.

IMHO, a common .dtsi made sense if both the boards went to production
and are largely available.

device-tree sources continue to get updates even though hardware itself
is pretty much frozen. am335x-bone-common.dtsi created 3 years back is
receiving updates still - as recently as 3 months back. So, I do expect
that A2 will need to get tested in many years to come. Not sure if it
really worth that much effort.

Thanks,
Sekhar

  parent reply	other threads:[~2016-09-06 10:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  9:05 [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
2016-09-02  9:05 ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations Nishanth Menon
2016-09-02 10:18   ` Sekhar Nori
2016-09-02 14:52     ` Nishanth Menon
2016-09-02  9:06 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1 Nishanth Menon
2016-09-02  9:58   ` Tomi Valkeinen
2016-09-02 10:01     ` Nishanth Menon
2016-09-02 11:48       ` Tomi Valkeinen
2016-09-02 10:41   ` Sekhar Nori
2016-09-02 11:18     ` Tomi Valkeinen
2016-09-02 13:52     ` Robert Nelson
2016-09-02 15:01       ` Nishanth Menon
2016-09-02 15:06       ` Tony Lindgren
2016-09-06 10:10       ` Sekhar Nori [this message]
2016-09-06 20:05         ` Tony Lindgren
2016-09-07  5:09           ` Sekhar Nori
2016-09-02  9:14 ` [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon

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=84be68f4-c5a6-0afe-c402-1adba9172918@ti.com \
    --to=nsekhar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).