public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] remove RaspberryPi support
Date: Tue, 12 Feb 2019 13:41:11 +0100	[thread overview]
Message-ID: <a90a476d-b860-76f8-27e1-992295c748ec@siemens.com> (raw)
In-Reply-To: <20190212113919.GI805@yssyq.m.ilbers.de>

Hi Baurzhan,

On 12/02/2019 12.39, Baurzhan Ismagulov wrote:
> On Tue, Feb 12, 2019 at 10:30:36AM +0100, claudius.heine.ext@siemens.com wrote:
>> RaspberryPi is removed from meta-isar, because
>>   - there currently no maintainers for it
>>   - there is no automated boot test for it
>>   - forces burden on rest of isar to support jessie
>>   - very old board, most users should have moved on to RPi 2 or 3
>>
>> If those points change, support for it can be readded.
> 
> - There is a maintaner (the process has to be improved)

Well the issue to update rpi to stretch in gh is open for 1.5 years.

> - Testing doesn't have to be automated (automation desired mid- to long-term)
> - There is value in supporting old boards as long as it is reasonable
> - I think we should strive for evolution and not discrete add-remove jumps
> 
> The burden issue demonstrates one of the fundamental ideas behind Isar. After
> some time, people end up building for different suites. Many people who release
> stretch today will build for stretch and buster tomorrow. Maybe now is the time
> to make pluggable mechanisms for different suites. Without satisfying that
> need, Isar won't be serving people in the long run, IMHO.

No. IMO you should use an old version of isar for old stuff. Trying to 
be backwards compatible as long as possible it not something isar<1.0 
should try to do anyway, but I would argue that isar>1.0 should also 
restrict.

Isar breaks the layer interface currently to often that it does not make 
any sense to be coy about breaking board support if necessary.

> Regarding rpi1, I'd be reluctant to remove without understanding what went
> wrong first. Moving to stretch shouldn't be a problem, but the issue of
> elegantly supporting different suites remains nonetheless.

Great if updating rpi to stretch is not a problem, then this patch is 
not needed!

Well my intention for the removal patch was, that it will take about a 
week before it is merged and if raspberry pi is updated to stretch 
before that, then this patch is no longer needed.

I submitted this revision of the patch after I saw that the issue to 
upgrade rpi to stretch is now 1.5 years old. And I really don't want to 
wait such periods until we can drop jessie support. I hope you understand.

regards,
Claudius




-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2019-02-12 12:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 12:41 [Discussion] Deprecating Raspberry Pi Claudius Heine
2019-02-11 12:48 ` Jan Kiszka
2019-02-11 13:30   ` Claudius Heine
2019-02-11 13:51 ` [PATCH] remove raspberry support claudius.heine.ext
2019-02-11 14:03   ` Jan Kiszka
2019-02-12  9:30     ` [PATCH v2] remove RaspberryPi support claudius.heine.ext
2019-02-12 11:39       ` Baurzhan Ismagulov
2019-02-12 12:41         ` Claudius Heine [this message]
2019-02-12 16:40           ` Baurzhan Ismagulov
2019-02-12 16:49             ` Claudius Heine
2019-02-17 10:16               ` Baurzhan Ismagulov
2019-02-11 14:03 ` [Discussion] Deprecating Raspberry Pi Baurzhan Ismagulov
2019-02-11 14:11   ` Claudius Heine
2019-02-11 14:27     ` Baurzhan Ismagulov
2019-02-11 15:17       ` Claudius Heine
2019-02-17 10:44 ` Baurzhan Ismagulov
2019-02-18  8:44   ` Claudius Heine

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=a90a476d-b860-76f8-27e1-992295c748ec@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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