Conversation

I would like to drop armhf (armv6) support in . The only current hardware I am aware of that is armv6 is Raspberry Pi Zero series (EOL 2030). I don't think it is worth the extra effort to support both armhf (armv6) and armv7 at this point.

Do you think we should drop armhf to free up some resources?

0% Lets drop both armhf and armv7 (no 32 bit arm)
100% Lets drop armhf (armv6) but lets keep armv7
0% NOOOOO! Lets keep both armhf and armv7!!!!!
7
7
0

It was brought to my attention that rpi 1 is still produced, which also uses armv6

1
1
0

@ncopa which kind of resources, build infrastructure or manpower?

1
0
0
@ncopa on @postmarketOS side, I looked at the wiki for armhf devices that may be impacted by armhf dropping.

postmarketOS supports 28 armhf devices. Out of all 28 armhf devices, 26 are actually armv7 running an armhf kernel/userspace for legacy reasons, and should be moved to armv7. Out of these, only one runs a mainline kernel.

The remaining 2 are the RPi1 and zero.
1
0
4

@ncopa Debian dropped armv6 support. So there is not much left.

Is Alpine still using 32bit time_t?

1
0
0

@ncopa what other options of Linux flavor (short of something like LFS) exist for armv6 if alpine drops support at this point?

3
0
0

@gfaster @ncopa I don't know, but the support is dropping in the whole Linux ecosystem. this is the whole reason why were thinking of dropping it: less and less people care

1
0
0

@fossdd @Nero yeah, reduce friction. More and more upstream drop support for it.

It would also help a little bit in disk usage on mirrors which is becoming a problem, and CI resources. None of those would make big difference but it is a little here and there.

One less thing to worry about.

0
0
0

@waldi @ncopa no, musl already bit the bullet and uses 64bit time_t

0
0
0

@fun @ncopa @postmarketOS This was my concern as well.

1
0
0

@ncopa In the embedded/industrial space I'm still seeing a surprising amount of ARM9 and expect those to go on quite a while, but that'd be v5, so even older. v7 seems like a more sensible target for Alpine 32bit support than trying to keep that /and/ v6 on life support together.

0
0
0

Orca 🌻 | 🎀 | 🪁 | 🏴🏳️‍⚧️

@ncopa@fosstodon.org My oldest device is on ARMv7. But can you also check with the pmOS devs to see if they have supported ARMv6 devices?
1
0
0
@gfaster @ncopa i'd say dietpi maybe though that's more SBC focused, and also debian based & apparently they've also dropped support for armv6 too
0
0
0

@socketwench @fun @ncopa @postmarketOS

That seems like a reason to drop armv6, so somebody is finally motivated to move those devices to armv7 :)

1
0
0

@pabloyoyoista [looks around at ram and storage prices]

Somehow, deprecating old hardware doesn't seem timely right now.

2
0
0

@gfaster @ncopa Gentoo linux and TinyCore Linux but TinyCore has no version 17 arm build yet

0
0
0

@fossdd @ncopa I have a rpi zero that I want to set up (I haven't yet, hence why I haven't voted, I have no skin in the game yet), it just seems like it'd be a shame to brick

0
0
0
@socketwench @pabloyoyoista what hardware supported by pmOS would be deprecated by this change?
0
0
0
@Orca @ncopa it wouldn't really affect us. We have a few armhf device ports but as it turns out all of them with the exception of two, actually target armv7-capable devices, so they should be moved to armv7. The two remaining are the Pi0 and Pi1. (see my post about this somewhere else in this thread)
0
0
0

@socketwench I would consider deprecating 2 out of something like 500+? to be a pretty fine tradeoff. The other 26 just need a bit of work on software to keep working if anybody has the interest

0
0
0