@a1ba unsarcastically, I like that.

• But then again I'm a sucker for non-#AMD / #Intel #ix86 / #amd64 #CPU|s and non-#AMD / #Intel / #nvidia / #3dfx (wallet sez so!) #GPU|s.

• Like some #Transmeta / #VIA / #Vortex86 / #Cyrix / #Xiaoxin CPU with like a #SiliconMotion / #ASPEED / #Matrox / #S3 GPU added to it.

Won't run Crysis, but will run @OS1337!

Funnily enough, it takes more than 5 minutes to bump the char limits on Mastodon's toots

It's been compiling for ages (I'm just bumping to 1000) and doesn't seem to get anywhere, almost as if it was stuck for the arm64 target

On the other hand, the amd64 target is working like a charm, so I guess it has to do with architecture emulation ?

#mastoadmin #mastodon #arm64 #amd64 #selfhosted #fediverse

I recently took a dive into #C11 #atomics to come up with alternative queue implementations not requiring locking some #mutex.

TBH, I have a hard time understanding the #memory #ordering constraints defined by C11. I mean, I code #assembler on a #mos6502 (for the #c64), so caches, pipelines and all that modern crap is kind of alien rocket science anyways 😆.

But seriously, they try to abstract from what the hardware provides (different kinds of memory barrier instructions, IMHO somewhat easier to understand), so the compiler can pick the appropriate one depending on the target CPU. But wrapping your head around their definition really hurts the brain 🙈.

Yesterday, I found a source telling me that #amd64 (or #x86 in general?) always has strong ordering for reads, so no matter which oderding constraint you put in your atomic_load and friends, the compiler will generate the same code and it will work. Oh boy, how should I ever verify my code works on e.g. aarch64 without owning such hardware?

Very cool to see #riscv support coming to #redhat distributions. 😎

#ubuntu on the same train as well, but we need more widespread adoption for it. The faster we get there, the faster we can remove #arm and #amd64 from being the core #ISA used. 😉
https://www.sifive.com/press/sifive-collaborates-with-red-hat-support-enterprise-linux-risc-v

@jbqueru OFC and in terms of #RISCv vs. #ARM it won't be competitive for quite some time as ARM includes a lot of #proprietary and #patented #PowerSaving technologies that are just not available outside of said closed ISA.

• I do thus treat #ARM64 like #amd64: A "black box" that I cannot audit, verify or control beyond what it allows me to.

@jbqueru Also I hope for #RISCv to be the #ISA of the future for long-term #OpenSourceHardware and support.

#ARM64 - just like #amd64 - is yet another proprietary ISA and almost all devices with it in terms of #Laptops have #AntiRepairDesign like #Apple's #MacBook|s that self-destroy their #SSD|s which also contains it's #EFI / "#BridgeOS", making machines with fried SSDs 'braindead'…

And yes, #RAM to also fails and making it not fully replaceable and upgradeable is inherently bad and I'm still mad at @frameworkcomputer for their botched #FrameworkDesktop #PC!

• Cuz it's neither necessary nor beneficial for a #Desktop PC, unlike with the #Framework12 where the #SoC used only supports single channel and a single SODIMM so it makes sense for them to take that into account.

@pauliehedron @BrodieOnLinux I daily drive a #hp #t620 as a mini server, because in #Germany power is expensive af and I want something cheap (€30 used), quiet (fanless!) and having #amd64 durig the #PiShortage.

• And yes, it'll even run @tails_live / @tails / #Tails and @torproject / #Tor if you are patient with it ir chug in a 2nd 4GB RAM stick in it.

5 lines of #JuliaLang is all you need to get to get the most of your hardware via #AVX512, #AppleSilicon, or other microarchitecture-specific binaries instead of plain #x86_64 / #amd64 / #x64, #aarch64 / #arm64 binaries!

… and the best part, you don’t even have to write those five lines - they’re here for you (and have been for a long time):

https://github.com/JuliaPackaging/Yggdrasil/blob/master/platforms/microarchitectures.jl

Updated version of my x86 prefixes and escape opcodes flowchart (now with APX):

https://soc.me/interfaces/x86-prefixes-and-escape-opcodes-flowchart

#asm #assembly #x86 #amd64 #compiler

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii Exactly...

Coincidentially, that's why #Android (and #iOS) doesn't let users have #root access because billions of devices owned by mostly "#TechIlliterates" that hardly get #SecurityUpdates would be an even bigger risk if they didn't boot a locked-down #ROM image, thus only allowing for #malware in user-privilegued userspace!

• I'd even go so far that I'd wish for @torproject to basically merge fmr. #FirefoxOS / #KaiOS & @tails_live / @tails / #Tails to build a #privacy-focussed #ROM for #Smartphones and #Tablets i.e. "#TailsMobile" or sth.

Cuz having a mobile OS that shoves everything through #Tor and only allows #userspace-Apps in the form modern web technologies would be a big #security and #privacy gain.

• Not to mention #amd64 is on it's way out and inevitably they gotta have to transition to supporting #arm64 and eventually #RISCv-#64bit at some point.

Just finished to upgrade five #AWS #EKS clusters to use a new CPU architecture for the nodes. From #AMD64 to #ARM CPU. Everything went smoothly, thanks to the usage of #Moby #BuildKit to generate multi-arch #OCI images !

@asmw uf yiu don't need #amd64 maybe there's some #arm64 board fir @frameworkcomputer ?

• Most of the "#magic" of #ARM is a shitload of patented power savings...

Blows my mind that I can use my AMD Ryzen laptop to build a container that will ultimately run on an Nvidia Jetson Orin NX (arm64). What were we doing before Docker was a thing?
#docker #crosscompile #arm64 #amd64

@riley @frameworkcomputer heard of it, sadly I need #amd64 hardware.

@vetgaming @linuxmint It's just a necessity, according to @fuchsiii, as it's just not feasible longterm to collect rarer-and-rarer #VintageComputing hardware and rely on non-enforcement of copyright on #Abandonware.

• Plus whilst #Valve isn't antragonistic to #Proton / #DXVK repackagings, not relying on them is kinda important, as this setup also helps with otger applications that ain't strictly games or in setups that one may not want to be on the internet.

It makes #TheSims and #FightingIsMagic just work on anything that is #amd64 and has enough resources to throw at it.

64ビットの #DLL がC:\Windows\System32に入っている #AMD64 #Windows の怪 https://homoo.social/@boronology@social.penguinability.net/114008356417334878

A few tooters have asked me what my config is, at which I replied that I run the Fediverse, platform agnostic. Then one asked what one of my main horizontal display systems run, at which I now reply with

` uname -a`
{Linux devakprata 6.12.13-2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.12-18~mx23ahs (2025-02-10) x86_64 GNU/Linux}

**Note**
I left the results of

`cat /proc/cpuinfo` out since I would get that 16 times!!!

` cat /proc/meminfo `
{MemTotal: 31750332 kB
MemFree: 27996612 kB
MemAvailable: 29376500 kB
Buffers: 85900 kB
Cached: 1890756 kB
SwapCached: 0 kB
Active: 2357024 kB
Inactive: 892372 kB
Active(anon): 1546640 kB
Inactive(anon): 0 kB
Active(file): 810384 kB
Inactive(file): 892372 kB
Unevictable: 48 kB
Mlocked: 48 kB
SwapTotal: 6291452 kB
SwapFree: 6291452 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 156 kB
Writeback: 0 kB
AnonPages: 1273116 kB
Mapped: 719588 kB
Shmem: 273900 kB
KReclaimable: 67860 kB
Slab: 169900 kB
SReclaimable: 67860 kB
SUnreclaim: 102040 kB
KernelStack: 16160 kB
PageTables: 30512 kB
SecPageTables: 4112 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 22166616 kB
Committed_AS: 6017728 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 98420 kB
VmallocChunk: 0 kB
Percpu: 7680 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
CmaTotal: 0 kB
CmaFree: 0 kB
Unaccepted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 347964 kB
DirectMap2M: 7952384 kB
DirectMap1G: 24117248 kB}

and this screencap

#neofetch #sysinfo #POSIX #uname #Linux #Fediverse #federated #OpenSource #hardware #AMD #AMD64

@MaliciousCarp consider some #fanless #amd64 #ThinClient instead....

• The work great as mini-servers, can accept quite a lot of RAM and usually have at meast USB 3.0 & M.2 B-Key slots...

Release is coming - help us with testing!

https://www.armbian.com/newsflash/release-is-coming-3/

#release #upgrade #features #fixes #aarch64 #armhf #amd64 #riscv64 #embedded #linux #armbian #debian #ubuntu #xfce #gnome #kde

Some sort of of success. I could place #nolf2 with #wine. Had (obviously) to install the #i386 versions of the #mesa packages besides the #amd64 ones.
Shout-out to #kisak for their mesa backporting btw.
Just wide-screen support doesn't work well. Stuff gets cropped.

Maybe I give #lutris another try as well.