X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by lists.alpinelinux.org (Postfix) with ESMTP id 4306F5C6448 for ; Wed, 19 Sep 2018 14:43:15 +0000 (GMT) Received: by mail-oi0-f50.google.com with SMTP id 8-v6so5331014oip.0 for ; Wed, 19 Sep 2018 07:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ABc4jg72S+m2+rermULgiWGATcA/4+GZDxxeoUWZ3CA=; b=JdAYec3HsbfXJwjOcvrNRSPEXcpbkhIegyDdgADWo0U2oQbM+jGELb5zidqyFT7BMu ro/FBMwS72KksYPAZzo7l1TB/ACCiFGMaZ0+6UrbMwZDFVJa4/1jmuJPVoUs2LT1Eciq ri8ma9kKablifZHtbw7C5v61xVfNUy3wMvcNJEoKHwMomFTajdc/6o3z8VXC08m8sn54 lIfuC7CMg1U5f9FfLsFBjbnOXYPRkHEtrgY9/dIisMOPiVfb2n5YNTOnM+hmqc1DkDiU +qtvuehwm6a62f9hd6nfKJIqJpYCeyTlRYzoCf9J+L0V3YSF/Ff+8BZa+3hcJhZJnOa0 pQUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ABc4jg72S+m2+rermULgiWGATcA/4+GZDxxeoUWZ3CA=; b=XbHL0sjJi8DEVmb1lZQIWlbzzhNKwiI7mgJZR9t94Z3OrR7yQgqJZZ/8W425L5qecd V04NCOOuQ++KKWystRqfMgsB4QS3wE+5qGw55QsMhoLn2Udh1wuNcC/xyojuesU4sTAB e3hNa11RGqdQhb9DhpUOhLanSvXKiwwiy12SvsbrhDsklWP/xQBy4QpQTidRvjZi58eg qrqdHXBymyWojs3znINJuyzXbA+Ztj+28UcuYd+Rojn8dMnXpEQE78GvIEz4AtKko2HD +qD0sFn5snqL4ghqWsL7UychepCqMwj52bOALOlZu0JZTWYm5tpYw+d+jYfrDTDz+kxs liPg== X-Gm-Message-State: APzg51CQXh8/9GyUIUztVZbz9bdOE+su5BGTHr4lGp1yUeTTWCH88z1t Ky4DemFBiPB9x4T511N2kMCNg7ikEd0KyGGe7pw= X-Google-Smtp-Source: ANB0VdYWZPQB4JfUYpXe63Izw2Q187aWJYkLFLh8KQnNwzsJBfVH4LdwO7yNvH+djHZ2rvatTSIUnxzbqgYJw51oxUw= X-Received: by 2002:aca:6285:: with SMTP id w127-v6mr1904844oib.120.1537368194857; Wed, 19 Sep 2018 07:43:14 -0700 (PDT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 References: <144d0e30-3c17-66b9-b2b6-7671eb8b6f84@bitmessage.ch> <20180919154656.7c6dfb9b@ncopa-desktop.copa.dup.pw> In-Reply-To: <20180919154656.7c6dfb9b@ncopa-desktop.copa.dup.pw> From: =?UTF-8?Q?Timo_Ter=C3=A4s?= Date: Wed, 19 Sep 2018 17:43:02 +0300 Message-ID: Subject: Re: [alpine-devel] Alpine and armv7 To: Natanael Copa Cc: Oliver Smith , alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000024c02305763a6df9" --00000000000024c02305763a6df9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi On Wed, 19 Sep 2018, 16.47 Natanael Copa, wrote: > On Wed, 19 Sep 2018 14:38:56 +0300 > Timo Ter=C3=A4s wrote: > > > Hi, > > > > I think we have the triplet already in scripts and everywhere. It is ju= st > > matter of starting builders and making sure all builds. Maybe add > arch=3Darm > > that covers armhf and armv7. > > > > I suppose the main reason for going with armv6 was rpi1 which was the > only > > rpi at the time. > > > > We had also limited build power for arm, but the situation is much bett= er > > now with aarch64 builders that can do arm too. > > > > 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 ma= ny > > care of armv7+ or armv4 only... > > > > I would be in favor of starting armv7 builders now. And maybe drop armh= f > a > > release cycle or two. > > > > @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. > Let's keep armhf still for a while. I suggest we bootstrap armv7 on x86-64 and start new builder edge/armv7. Once all builds, we can poll how many still need armhf. And yes armv7 is more common now than armhf. Raspbian originally was armhf equivalent. Rpi1 was the only major benefiter. I can bootstrap armv7 packages. And put them somewhere. Meanwhile, we probably want to patch aports to change all arch places from armhf to armhf+armv7, or potentially add "arm" as umbrella for all the 32bit arm builds and change armhf to that. Maybe someone can do that while I prepare the initial package set cross built. Timo > > > -nc > > > On Wed, 19 Sep 2018, 10.27 Oliver Smith, > > wrote: > > > > > 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 resul= t > > > 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 th= an > > > 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 > > > --- > > > > > > > > --00000000000024c02305763a6df9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Wed, 19 Sep 2018, 16.47 Natanael Copa, <ncopa@alpinelinux.org> wrote:
On Wed, 19 Sep 2018 14:38:56 +0300
Timo Ter=C3=A4s <timo.teras@gmail.com> wrote:

> Hi,
>
> I think we have the triplet already in scripts and everywhere. It is j= ust
> matter of starting builders and making sure all builds. Maybe add arch= =3Darm
> that covers armhf and armv7.
>
> I suppose the main reason for going with armv6 was rpi1 which was the = only
> rpi at the time.
>
> We had also limited build power for arm, but the situation is much bet= ter
> now with aarch64 builders that can do arm too.
>
> I was just making chrome build on armhf, but seems very tricky to do a= rmv6
> build of it. I ended up shipping armv7 build in armhf for now. Seems m= any
> care of armv7+ or armv4 only...
>
> I would be in favor of starting armv7 builders now. And maybe drop arm= hf a
> release cycle or two.
>
> @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.

<= div dir=3D"auto">Let's keep armhf still for a while. I suggest we boots= trap armv7 on x86-64 and start new builder edge/armv7. Once all builds, we = can poll how many still need armhf.

And yes armv7 is more common now than armhf. Raspbian originall= y was armhf equivalent. Rpi1 was the only major benefiter.

I can bootstrap armv7 packages. And put = them somewhere.

Meanwhil= e, we probably want to patch aports to change all arch places from armhf to= armhf+armv7, or potentially add "arm" as umbrella for all the 32= bit arm builds and change armhf to that. Maybe someone can do that while I = prepare the initial package set cross built.

Timo





-nc

> On Wed, 19 Sep 2018, 10.27 Oliver Smith, <ollieparanoid@bi= tmessage.ch>
> wrote:
>
> > 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 propose= d on
> > the ML in 2015 [1], but not really with a result. I've also t= alked to a
> > few Alpine developers independently about it, and each time the r= esult
> > 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 givi= ng them
> > a good speed improvement and smaller binaries due to thumb2.
> >
> > A more specific use case would be QT's QML framework, which h= as 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. Othe= r than
> > that, most arm devices are armv7 ones.
> >
> > * Replace armv6 with armv7? Or provide it as additional architect= ure?
> >
> > Initially I would have preferred to have armv7 as additional
> > architecture. But of course that means it needs twice the resourc= es, 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.alpineli= nux.org/alpine-devel/5036.html
> > [2]: https://gitlab.com/postm= arketOS/pmaports/issues/75
> >
> >
> >
> > ---
> > Unsubscribe:=C2=A0 alpine-devel+uns= ubscribe@lists.alpinelinux.org
> > Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alp= ine-devel+help@lists.alpinelinux.org
> > ---
> >
> >=C2=A0

--00000000000024c02305763a6df9-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---