On Mon, Nov 20, 2017 at 09:37:10AM +, Lars Brinkhoff wrote:
> My StrongARM-based Netwinder machine has been lying dormant for a while,
> but I was planning to bring it back up. It's ARMv4 without Thumb.
Does a netwinder have enough ram these days to run the installer (or
much of anything
Adrian Bunk wrote:
> If anyone is running stretch, buster or sid on ARMv4t hardware, then
> please let us know what device and kernel you are using and whether
> you intend to use buster.
My StrongARM-based Netwinder machine has been lying dormant for a while,
but I was planning to bring it back
On Mon, Nov 20, 2017 at 09:37:10AM +, Lars Brinkhoff wrote:
> Adrian Bunk wrote:
> > If anyone is running stretch, buster or sid on ARMv4t hardware, then
> > please let us know what device and kernel you are using and whether
> > you intend to use buster.
>
> My StrongARM-based Netwinder
On Sat, Nov 11, 2017 at 09:03:04PM +0100, Andreas Henriksson wrote:
> Hello,
>
> On Tue, Nov 07, 2017 at 11:10:27PM +0200, Adrian Bunk wrote:
> [...]
> > This whole "so many packages are broken on armel" narrative
> > is actually mostly FUD, and you are suggesting mitigations
> > for a
Hello,
On Tue, Nov 07, 2017 at 11:10:27PM +0200, Adrian Bunk wrote:
[...]
> This whole "so many packages are broken on armel" narrative
> is actually mostly FUD, and you are suggesting mitigations
> for a nonexisting problem.
>
> The only major package where armel is the only release
std::future was fixed a while ago by upstream. It now works on any target even
when there are no lock-free atomics in hardware.
See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735
Btw, prior that, you would actually need at least ARMv7.
Adrian
> On Nov 9, 2017, at 6:40 PM, Sune Vuorela
Hi,
Adam Borowski:
> On Tue, Nov 07, 2017 at 11:16:41AM +0100, John Paul Adrian Glaubitz wrote:
>> I think a possible solution is the plan we had inside Debian Ports which is
>> to introduce a Britney instance within Debian Ports and hence be able to
>> provide a Debian testing release.
>>
>> My
On Tue, 07 Nov 2017 20:44:08 +0200, Adrian Bunk wrote:
> > > for the armel port in buster the question of raising the baseline came up.
> > That has been a recurring question over the time, the reason to
> > maintain ARMv4t instruction set was OpenMoko mobile phone, which lot
> > of people was
On Tue, Nov 07, 2017 at 07:45:35PM +, Wookey wrote:
>...
> I'm very happy if people mark problematic packages that no longer
> build for armv5 as 'notforus' if no-one steps up to fix them in a
> timely fashion, but killing the architecture because some upstreams
> no-longer care about v5 seems
On 2017-11-07 11:48 +0100, W. Martin Borgert wrote:
> On 2017-11-07 11:08, Julien Cristau wrote:
> > Keeping armel on life support for 2 more
> > years is a significant drain on DSA and our hosters, for questionable
> > benefit.
>
> I agree, that this support comes not for free, but the benefit
>
On Tue, Nov 07, 2017 at 11:08:39AM +0100, Julien Cristau wrote:
>
> That's not clear to me at all. Keeping armel on life support for 2 more
> years is a significant drain on DSA and our hosters,
>...
What kind of significant drain exactly?
AFAIK so far noone has stated that it would be safe to
On Tue, Nov 07, 2017 at 01:43:50PM +0100, Héctor Orón Martínez wrote:
>...
> 2017-11-05 22:32 GMT+01:00 Adrian Bunk :
>
> > for the armel port in buster the question of raising the baseline came up.
>
> That has been a recurring question over the time, the reason to
> maintain
W dniu 07.11.2017 o 14:11, Thomas Goirand pisze:
> On 11/05/2017 10:32 PM, Adrian Bunk wrote:
>> 20 years ago you could go into a shop and buy a mobile phone
>> with a CPU supported by the armel port in stretch.
> I didn't know Stretch was released 20 years ago. :)
Stretch maybe not. But ARMv4t
On Tue, Nov 07, 2017 at 12:00:42PM +0100, Adam Borowski wrote:
> It would be great -- I tried to make an unofficial Jessie release for x32,
> but doing the equivalent of Britney turned out to be too hard. The main
> reason was binNMUs: any out-of-archive binNMU conflicts with official
> binNMUs
On 11/05/2017 10:32 PM, Adrian Bunk wrote:
> 20 years ago you could go into a shop and buy a mobile phone
> with a CPU supported by the armel port in stretch.
I didn't know Stretch was released 20 years ago. :)
Cheers,
Thomas Goirand (zigo)
On Tue, Nov 07, 2017 at 01:43:50PM +0100, Hector Oron wrote:
>
>Also build daemons are aging, those were initially donated by Marvell
>(some development boards) which then they replaced with other
>development boards. We have been unable to find suitable hardware to
>build armel port and current
>>>[+debian-embedded, feel free to adjust CC'd mailing lists on reply]
Hello,
Thanks for bringing up this discussion! And apologies for adding
more complexity to the initial question.
Find few comments inlined below,
2017-11-05 22:32 GMT+01:00 Adrian Bunk :
> for the armel
Quoting "W. Martin Borgert" :
There is still relevant hardware
around which can run "armel", but not "armhf".
Forgot to mention some, that one can still buy:
On https://www.taskit.de/stamp-overview.html the three boards
named "9261", "9G20", and "9G45". AFAIK.
Also
On Tue, 2017-11-07 at 02:49 -0800, Rick Thomas wrote:
> How do I know if a machine is ARMv4t? I have a sheevaplug and a
> couple of openrd machines (one “client”, the other “ultimate”) that
> are still doing useful work. Are they v4t?
They're ARMv5 (so still need armel). I too have similar
> On Nov 7, 2017, at 3:27 AM, Christian Seiler wrote:
>
> Hi,
>
> Am 2017-11-07 11:49, schrieb Rick Thomas:
>> How do I know if a machine is ARMv4t? I have a sheevaplug and a
>> couple of openrd machines (one “client”, the other “ultimate”) that
>> are still doing useful
Hi,
Am 2017-11-07 11:49, schrieb Rick Thomas:
How do I know if a machine is ARMv4t? I have a sheevaplug and a
couple of openrd machines (one “client”, the other “ultimate”) that
are still doing useful work. Are they v4t?
cat /proc/cpuinfo should do the trick. It might not show the 't'
after
How do I know if a machine is ARMv4t? I have a sheevaplug and a couple of
openrd machines (one “client”, the other “ultimate”) that are still doing
useful work. Are they v4t?
Thanks,
Rick
> On Nov 5, 2017, at 1:32 PM, Adrian Bunk wrote:
>
> Hi,
>
> for the armel port in
On Tue, Nov 07, 2017 at 11:16:41AM +0100, John Paul Adrian Glaubitz wrote:
> I think a possible solution is the plan we had inside Debian Ports which is
> to introduce a Britney instance within Debian Ports and hence be able to
> provide a Debian testing release.
>
> My dream would be to not to
On 2017-11-07 11:08, Julien Cristau wrote:
> Keeping armel on life support for 2 more
> years is a significant drain on DSA and our hosters, for questionable
> benefit.
I agree, that this support comes not for free, but the benefit
is not questionable to me: There is still relevant hardware
On 11/07/2017 11:08 AM, Julien Cristau wrote:
That's not clear to me at all. Keeping armel on life support for 2 more
years is a significant drain on DSA and our hosters, for questionable
benefit.
I think a possible solution is the plan we had inside Debian Ports which is
to introduce a
On 11/05/2017 10:32 PM, Adrian Bunk wrote:
> Hi,
>
> for the armel port in buster the question of raising the baseline came up.
>
> 20 years ago you could go into a shop and buy a mobile phone
> with a CPU supported by the armel port in stretch.
>
> Roger Shimizu is doing a great job on ARMv5
Hi,
for the armel port in buster the question of raising the baseline came up.
20 years ago you could go into a shop and buy a mobile phone
with a CPU supported by the armel port in stretch.
Roger Shimizu is doing a great job on ARMv5 hardware and I've seen bug
reports from users on ARMv5
27 matches
Mail list logo