Suuri kokeilupäivä! Kaksi #RaspberryPi'ta, 2B+ (#armv7) ja 4 (#aarch64). Kolme kokeiltavaa järjestelmää, #AlpineLinux 3.23, #FreeBSD 15.0 ja #NetBSD 10.0 (vain uudempaan RasPiin). Tästä tulee hauskaa. #floss #linux #bsd #atkjuttuja
#Armv7
So I didn't realize the EOL for #homeassistant #armv7 also referred to the docker images they publish. Anyone maintaining a fork to keep them published a while longer?
Raspberry Pi
A relatively underwhelming ARM development board to begin with that was upgraded to a very reasonably performing quad-core CPU in February 2015 and got built-in Wi-Fi in February 2(...)
#aarch64 #arm #armhf #armv6 #armv7 #armv8 #bcm2711 #bcm2835 #bcm2836 #bcm2837 #hardware #raspberrypi #rp3a0 #sbc #singleboardcomputer
Ah yes, because who doesn't want to spend their weekend parsing ELF headers and translating memory access while pretending they understand #Armv7 CPU emulation? 🤓 By the end of this 8,336-word epic, you'll be the life of the party with your newfound ability to forward syscalls and handle exception exits. 🎉 #Goals
https://xnacly.me/posts/2025/building-a-minimal-viable-armv7-emulator/ #ELFheaders #emulation #syscall #handling #techenthusiast #weekendproject #HackerNews #ngated
Building a Minimal Viable Armv7 Emulator from Scratch
https://xnacly.me/posts/2025/building-a-minimal-viable-armv7-emulator/
#HackerNews #Building #Minimal #Viable #Emulator #Armv7 #Scratch #Technology #Development
🌘 從零開始打造最小可行ARMv7模擬器
➤ 以Rust實作極簡ARMv7使用者模式模擬器，深入解析ELF與ARM指令
✤ https://xnacly.me/posts/2025/building-a-minimal-viable-armv7-emulator/
作者以Rust語言從零開始，不依賴任何外部函式庫，建構了一個極簡的ARMv7使用者模式模擬器。此模擬器能解析ARMv7的ELF二進位檔，載入其記憶體區段，解碼並模擬執行部分ARMv7指令，並將訪客（guest）記憶體存取轉換為主機（host）記憶體存取。此外，它還能攔截並轉發ARM Linux系統呼叫至x86-64的System V系統呼叫。作者成功地用此模擬器執行了一個「hello world」ARMv7二進位檔，展示了其效率與可行性，並藉此深入理解ELF格式、ARM指令編碼及二進位檔的執行流程。
+ 這篇文章對於想理解模擬器底層運作原理的人來說非常有價值！作者從零開始的堅持令人佩服。
+ Rust 在效能和安全性上的運用在這篇文章中展現得淋漓盡致，對於學習低階系統程式設
#軟體開發 #模擬器 #Rust #ARMv7
Hey #Fediverse, say Hi to Gale!
Gale is a 2016 #Google Wifi #router on the Fediverse. They're running #GoToSocial 20.1 on their quad-core #ARMv7 processor and 512MB of RAM.
You can visit Gale at @gale@gts-googlewifi.k3can.us and Gale will be posting daily facts about #Wifi and #Networking, so give 'em a follow!
For more info, see my blog posts at https://blog.k3can.us/tags/googlewifi/
I'm trying an #Armv7 install of #gotosocial and it seems to kind of work... Except that if I try to upload a photo, then the entire thing crashes. It also crashed once when I tried to update the Instance info screen (adding a description).
It's running on a small device, so I'm guessing that it's just spiking the CPU/RAM and that's causing the crash, but what's weird is that I don't see anything in the logs to suggest a problem, no OOM from the kernal, etc. It's just running one moment and then not running the next.
I've already reduced the cache target significantly and limited the media upload sizes... Is there a way to just disable media entirely? I'm fine with it being a text-only instance. Anyone have any other suggestions for running GTS on a stupidly small server?
#gotosocialhelp
Raspberry Pi
A relatively underwhelming ARM development board to begin with that was upgraded to a very reasonably performing quad-core CPU in February 2015 and got built-in Wi-Fi in February 2(...)
#aarch64 #arm #armhf #armv6 #armv7 #armv8 #bcm2711 #bcm2835 #bcm2836 #bcm2837 #hardware #raspberrypi #rp3a0 #sbc #singleboardcomputer
@jgoerzen yeah, in terms of absolute low power draw there may be something more power efficient than the #Pi0W2 (basically a cut-down #Pi3 A+) and #Pi0 / #Pi0W (a cut-down Pi 2 Model A)…
There should be lower power consuming yet more powerful (or at least more powerful at the same power draw) options already due to snaller structural width.
After all the Xbox 360 went from 203W to 120W during it's lifecycle despite getting the Kinect as additional power-drawing accessory burdened on.
Problem is that so far no "competitior" even came close to #RaspberryPi when it comes to #documentation.
- Like most of the time they just randomly release some #Android / #Linux image and tell buyers to 'feck off' when it comes to reproduceable builds or mainline #LinuxKernel support…
Whereas even some "old" 14nm node'd #ARMv5r11 or #ARMv7 / #ARM64 we'd all expect something that delivers a desktop @ 2W TDP like the Intel Atom x5-Z8350 did over a decade ago!
- I really appreciate your efforts and espechally #documentation as it makes it so much easier...
There's a reason I only considered architectures to build @OS1337 against that are "obtainable" and I'll prioritize those that I have in my possession and that can be cheaply acquired, which as of writing are about 12 build targets across 5 distinct ISAs ( #i486 and up, #amd64, #ARMv5r11, #ARMv7, #ppc64) , with only 1 (#i486SX) being currently in focus and the next one being the #Pi0 / #Pi0W who's code will run (abeit not performant) on the #Pi0W2 as well...
- All 3 #PiZero|s can be had for like €100 in total with shipping and SD-Cards so it's on-par with a useable #amd64 machine like a #ThinClient with proper SSD and RAM...
Also unlike any other #SBC manufacturer @raspberry_pi / #RaspberryPi actually write proper #documentation and not just fart out some random bootable image file and tell users to feck off!
ArmSoM CM1 is a $15 RK3506J compute module with an optional carrier board.
We’ve seen a bunch of computer-on-a-module designs from Raspberry Pi, Banana Pi, NVIDIA, and others in recent years. But the ArmSoM CM1 stands out as one of the only models I’ve seen that can be used with or without a carrier board since it has a built-in USB-C port, MIPI-DSI display connector, and microSD card reader.
It’s also pretty cheap, with prices starting at just $15 for a standalone […]
#armsom #armsomCmIo #armsomCm1 #armv7 #computeModule #RK3506J
Read more: https://liliputing.com/armsom-cm1-is-a-15-rk3506j-compute-module-with-an-optional-carrier-board/
Last chance to express your voice about 32-bit #ARM on #openSUSE? Take the survey now https://survey.opensuse.org #ARMv7 #RaspberryPi #BeagleBone
A tout hasard : quelqu'un à une idée de pourquoi en C++11
```C++
thread_local static QObject foo;
```
Ferait un segfault sur Armv7 mais pas sur x86_64 ?
QT5.15 ici. Pour le fluff, je rencontre ce cas dans qt5base/src/corelib/time/qtimezoneprivate_tz.cpp
dans QTzTimeZonePrivate::staticSystemTimeZoneId()
The Luckfox Pico Mini B – Linux in a Thumbnail
https://taoofmac.com/space/blog/2024/07/20/1800
#ycombinator #arm #armv7 #cortex_a7 #embedded #hardware #linux #luckfox #mcu #npu #rv1103
Is there someone that #crosscompile #linux #kernel with #rust for #armv7 or 32bit architecture?
Ich lerne gerade dass meine #Odroid #XU4 #SBC nur 32 Bit sind und #ARMv7 wird in #paperlessngx nicht mehr unterstützt. So habe ich erst mal die letzte Version 1.17.4 am laufen.
Das Ganze läuft auf einem dietpi.com Image im Docker mit Portainer.
Anyone interested testing #RunCPM on #Android >=5.x (because of the Termux-App)
with #ARMv7 CPU?
You could try the following archive:
https://drive.google.com/file/d/1G-x4cWhXsWdLTO0pUYCcvasg8A_smdbd/view?usp=sharing
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst