X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 8BA445C63D9 for ; Wed, 19 Sep 2018 13:47:02 +0000 (GMT) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 205349E1F5F; Wed, 19 Sep 2018 13:47:02 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 07FF89E03EB; Wed, 19 Sep 2018 13:47:00 +0000 (GMT) Date: Wed, 19 Sep 2018 15:46:56 +0200 From: Natanael Copa To: Timo =?ISO-8859-1?B?VGVy5HM=?= Cc: Oliver Smith , alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Alpine and armv7 Message-ID: <20180919154656.7c6dfb9b@ncopa-desktop.copa.dup.pw> In-Reply-To: References: <144d0e30-3c17-66b9-b2b6-7671eb8b6f84@bitmessage.ch> X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.31; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, 19 Sep 2018 14:38:56 +0300 Timo Ter=E4s wrote: > Hi, >=20 > I think we have the triplet already in scripts and everywhere. It is just > matter of starting builders and making sure all builds. Maybe add arch=3D= arm > that covers armhf and armv7. >=20 > I suppose the main reason for going with armv6 was rpi1 which was the only > rpi at the time. >=20 > We had also limited build power for arm, but the situation is much better > now with aarch64 builders that can do arm too. >=20 > I was just making chrome build on armhf, but seems very tricky to do armv6 > build of it. I ended up shipping armv7 build in armhf for now. Seems many > care of armv7+ or armv4 only... >=20 > I would be in favor of starting armv7 builders now. And maybe drop armhf a > release cycle or two. >=20 > @ncopa What do you think? I am in favor of this too. Do we need add armv7 while keeping armhf as armv6? Or can we simply replace the current armhf build with armv7? Then the triplet would correspond better with debian, if i understand things correctly. -nc > On Wed, 19 Sep 2018, 10.27 Oliver Smith, > wrote: >=20 > > Hello Alpine friends, > > > > > > how about providing packages for the armv7 architecture in Alpine? > > > > This has been discussed quite a few times in IRC and even proposed on > > the ML in 2015 [1], but not really with a result. I've also talked to a > > few Alpine developers independently about it, and each time the result > > was basically, that they would want that. > > > > Let me re-iterate the common talking points: > > > > * What's the advantage? > > > > Programs would be optimized for armv7 instead of armv6, thus giving them > > a good speed improvement and smaller binaries due to thumb2. > > > > A more specific use case would be QT's QML framework, which has a JIT > > compiler for armv7 but not for armv6 [2]. > > > > * Which devices are armv6 anyway? > > > > The most relevant ones would be the Raspberry Pi 1 and Zero. Other than > > that, most arm devices are armv7 ones. > > > > * Replace armv6 with armv7? Or provide it as additional architecture? > > > > Initially I would have preferred to have armv7 as additional > > architecture. But of course that means it needs twice the resources, and > > getting that out of thin air doesn't seem to be realistic for Alpine. So > > my opinion has shifted, I think replacing armv6 with armv7 would be nice > > already. > > > > Questions: > > * is there anyone who insists on Alpine keeping armv6 support? > > * what would be the steps required to get armv7 going with Alpine and > > how can I help out? > > > > > > Best regards, > > Oliver > > > > [1]: https://lists.alpinelinux.org/alpine-devel/5036.html > > [2]: https://gitlab.com/postmarketOS/pmaports/issues/75 > > > > > > > > --- > > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > > Help: alpine-devel+help@lists.alpinelinux.org > > --- > > > > =20 --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---