#486sx — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #486sx, aggregated by home.social.
-
🚀👴 In a stunning display of 2014-level ambition, we have a replica of a 486 SX, because apparently, someone thought the computing power of a 🦖 dinosaur was worth resurrecting. 🤔 Maybe next they'll tackle the truly riveting challenge of recreating a prehistoric fax machine core. 📠
https://github.com/alfikpl/ao486 #retrocomputing #technostalgia #486SX #innovation #hackernews #HackerNews #ngated -
🚀👴 In a stunning display of 2014-level ambition, we have a replica of a 486 SX, because apparently, someone thought the computing power of a 🦖 dinosaur was worth resurrecting. 🤔 Maybe next they'll tackle the truly riveting challenge of recreating a prehistoric fax machine core. 📠
https://github.com/alfikpl/ao486 #retrocomputing #technostalgia #486SX #innovation #hackernews #HackerNews #ngated -
ao486: x86-compatible Verilog core implementing all features of a 486 SX (2014)
https://github.com/alfikpl/ao486
-
ao486: x86-compatible Verilog core implementing all features of a 486 SX (2014)
https://github.com/alfikpl/ao486
-
Upozornění: tyto grafické materiály mohou pamětníky silně rozrušit! #dosgaming #486DX #486SX
-
Wow, @linux does actually improve efficiency over time...
I just compiled a minimal kernel 6.5 for OS/1337 targeting #i486 instead of #i686 and the resulting binary is even 10kB smaller than the one for 6.4.12...
For real: That's awesome cuz it allows me to make the #Floppy version for #486SX a reality and still have #Toybox & #dropbear as #SSH client in it...
Cudos to @torvalds and the maintainers for that:
They really did cleanup the codebase and made it #smol|ler! -
So for those asking, the #1440kB #Floppy Version of OS/1337 will be a better #Floppinux with #Ethernet & #Network support and packing in #Dropbear as #SSH client.
So you could at the very least use it as a #SSH #Terminal #distro...
Sadly this means it will require at least an #i686 and won't run on an #i486 anymore as a lot of memory was eaten up by #486SX workaround code in the kernel...
