public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [Discussion] Deprecating Raspberry Pi
Date: Mon, 11 Feb 2019 14:30:34 +0100	[thread overview]
Message-ID: <6fe727b6-3437-1242-9235-9b7bae86268e@siemens.com> (raw)
In-Reply-To: <a66e7108-2398-e502-7408-40102f405a8f@siemens.com>

Hi Jan,

On 11/02/2019 13.48, Jan Kiszka wrote:
[...]
>> 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.
> 
> The RPi1 is probably also an uninteresting target by now.

I agree.

> 
>>
>> 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.
> 
> Keeping a non-Debian target would have the value to stress our 
> abstractions. But that only works if the target is recent enough 
> (Stretch or newer), frequently built and run as well.

Yes. One additional point is if we have the man-power and will to 
support non-Debian distributions. And If we do, we have to ask if 
Raspbian is the most interesting one or if for instance Ubuntu for 
RPi2+3 would be more useful for people. Maybe we could stick to just VM 
targets in meta-isar, so that booting is easy to test.

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-11 13:30 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 [this message]
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
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=6fe727b6-3437-1242-9235-9b7bae86268e@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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