From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [Discussion] Deprecating Raspberry Pi
Date: Mon, 11 Feb 2019 15:11:27 +0100 [thread overview]
Message-ID: <990d9077-d17f-1a73-4f84-fb8fd80af73f@siemens.com> (raw)
In-Reply-To: <20190211140318.GB805@yssyq.m.ilbers.de>
Hi Baurzhan,
On 11/02/2019 15.03, Baurzhan Ismagulov wrote:
> On Mon, Feb 11, 2019 at 01:41:19PM +0100, Claudius Heine wrote:
>> is anybody currently using Isar to build for Raspberry Pi?
>>
>> If that target is not maintained and used, then I would be in favor of
>> removing it from meta-isar.
>>
>> I just tried to boot the 'isar-image-base.rpi-sdimg' image of the current
>> next branch (d88c739323ecdecc) on a Raspberry Pi 1 without success.
>>
>> Currently RPi support with jessie is holding us back to deprecate jessie and
>> removing the loop mounts that is required by the old versions of mkfs.ext4.
>> So I would be in favor of eigher removing RPi1 support or switching to
>> stretch with that, if there are maintainers that regularly test if booting
>> works.
>
> FWIW, I'm still using rpi1. I agree it should at least be updated. I also find
> Raspbian to be a good test case for flexibility of Isar, so I'd like to keep
> it; that doesn't prevent us from adding Ubuntu support as well. Let me check
> what has to be done for the update.
Ok, since you are using it, and it currently does not boot AFAIK, does
that mean it is not tested regularly? IMO to have upstream support for a
board means that it should be tested in the CI or similar as well.
Otherwise it can be supported outside of Isar.
If you are willing to maintain RPi1 support then I have nothing against
leaving it in upstream Isar.
Cheers,
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
next prev parent reply other threads:[~2019-02-11 14:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 12:41 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
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 [this message]
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=990d9077-d17f-1a73-4f84-fb8fd80af73f@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