Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id A4F73782B20 for <~alpine/devel@lists.alpinelinux.org>; Fri, 29 May 2020 05:08:43 +0000 (UTC) Date: Fri, 29 May 2020 05:08:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1590728922; bh=mS8yxQjWwjSLf2wKAoEH5LXRmZm+prfm+ksr1ah8bwY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=ksK4Pwo3ipcmnYZ0sMy/I+GPLewv2KXEFe4XQVueVhf6eq35i/+WNT469GV1349XV 5wA5gDtETroRxFAlMg/fGjVz330Ai+1Y7PO1Z3oQE+3AyFuSBYQY1udCJlqHK4/5L0 nBB5oP+sEkaN1i/0fZgVLQ/4LPsFFj26z7XN4U6Y= To: Natanael Copa From: Mogens Jensen Cc: Alpine develmopment <~alpine/devel@lists.alpinelinux.org> Reply-To: Mogens Jensen Subject: Re: Can we drop armhf (armv6) after v3.12? Message-ID: In-Reply-To: <20200528104748.4d37ede5@ncopa-desktop.copa.dup.pw> References: <20200528104748.4d37ede5@ncopa-desktop.copa.dup.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Thursday, May 28, 2020 8:47 AM, Natanael Copa wr= ote: > Hi! > > Can we drop the armhf architecture after 3.12 release? > > It means that we will continue support armfh with 3.12 for two mor > years, but edge and next release 3.13 will be without armhf. > > This means that we effectively drop support for Raspberry pi 1 and > raspberry pi zero which are armv6. This is also the hardware we have > kernel for. > > The reason is that there are increasing number of issues that are not > fixed upstream. For example: > https://bugreports.qt.io/browse/QTBUG-65246 > > We will also need to rebuild all our 32 bit architectures from scratch > when upgrading to musl 1.2 due to time64. It requires significant > effort to do that and it would be nice to only need to do it for x86 > and armv7, and drop armhf. > > Are there any good reasons to why we should keep armhf? > > Are there other reasons to why we should drop it? > > -nc > > PS. This was previously been discussed for 3.10 release: > https://lists.alpinelinux.org/~alpine/devel/<20190404112525.4b04fdeb%40nc= opa-desktop.copa.dup.pw># It would be very sad to see armhf dropped from Alpine. BusyBox, uClibc/musl and as it says on the frontpage "Small. Simple. Secure", Alpine has always been about small and embedded devices, so if now support is going to be removed for some of the most famous embedded systems, then what's the point? There are millions of Raspberry Pi 1, Zero and ZeroW that can have a long and useful life with Alpine. There are NO lightweight and systemd free distro that are as good as Alpine for these devices (or anything else). Most of them lives as small headless servers or do embedded work, so as already suggested in this thread, maybe there is a middel ground of not supporting problematic UI stuff? Thanks to everyone working on Alpine Linux. Regards, Mogens Jensen