Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

272
active users

toad.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#arm64

4 posts4 participants2 posts today
Public
Raunak

Wrote a minimal HTTP server with sendfile support in ARM64 assembly. Started with a simple Zig server and ported to assembly syscall by syscall. Mostly straightforward but took a while to figure out memory related instructions and how to work with structs in assembly.

code: gist.github.com/rrampage/d31e7

Compiles to ~620 byte binary after `sstrip -z`

currently, it just serves an index.html. Will probably get around to adding `getdents64` support and maybe some multi-threading with `epoll` support

Here's a screenshot of serving a Game of Life WASM demo from a 10 year old android phone running this server

ARM64 HTTP server serving a 1.6 MB Game of Life wasm demo written using raylib
#zig#arm64#linux
Public
DocYeet :verified:

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
Replied in thread
Public *
Kevin Karhan :verified:

@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.
YouTubeThe design of Apple's soldered in SSDs is worse than I thought!By Louis Rossmann
#desktop#framework12#soc
Public *
Michael Dexter

The recording of the April 23rd, 2025 #bhyve Production User Call is up:

youtu.be/msJp73WRLq4

We discussed truncating large disk images, OpenPower planning, a new ESXi release, Haiku, a long-term networking issue and its progress, #FreeBSD 15.0-RELEASE goals, uboot/squashfs/uboot under #ARM64, debugging with GDB and bhyve, joining Production User Calls with FreeBSD and Wayland, and more!

"Don't forget to slam those Like and Subscribe buttons."

Public
Dave Neary

I'm writing an article on what kernel page size is, why you might want to use larger page sizes for certain applications, and how to do it. I'm interested in any feedback that #Arm64 users might have, or any experiences you can share: community.amperecomputing.com/

Ampere arm64 Developer Community · 64K Memory page sizes - any experiences to share?Hi all, I’m writing a fairly brief overview of the differences between 4K and 64K kernel page sizes - what a bigger kernel page size means, what types of applications benefit from larger contiguous chunks of memory, and how to use larger page sizes on various distributions. I’d love to hear feedback from anyone who has used larger page sizes, and whether they saw significant performance benefits for things like running VMs, databases, or AI inference workloads when running with 64K kernels - a...
ExploreLive feeds
About