@krutonium because it necessitates gracefully moving threads to one core and most power saving techniques like dynamic clocking that are done transparently by the CPU are more effectively.
@krutonium because it necessitates gracefully moving threads to one core and most power saving techniques like dynamic clocking that are done transparently by the CPU are more effectively.
@timixretroplays yeah, I guess this shows @rasteri build this before businesses started upgrading tech.
I wished DM&P / ICOP would increase production or that there was an easier way to get other #ix86 SBCs from like #VIA (remember when they made #CUP|s?) or some #embedded variants from #Intel or #AMD.
Cuz I was shure some #IntelAtom SoC's and #AMDGseries APUs do have #ISA support as they use quite older process nodes and microarchitectures.
But for a #MSDOS #RetroGaming system, that is quite a bottleneck to work on when it comes to #BareMetal.
#DOSBOX or similar do work well, but they don't provide the necessary I/O for a lot of use-cases.
Maybe you can drop in a different #Vortex86 which also has #ISA?
@cleverboi @FandaSin @BrodieOnLinux @neal to answer your question stuff like @rasteri 's #Wee86 * & #WeeCee ** are quite common in #embedded & #industrial setups because as much superior the #Atom Z520 and E3815 are, these have been discontinued unlike the #Vortex86 SoCs!
Yes, I hate #Microsoft & dislike the fact that people.use #MSDOS despite it being deprecated longer than #WindowsXP exists but someone's gotta have to do #DataRecovery or at least #backup & #restore said systems' drives...
https://infosec.space/@kkarhan/114738983433662865
@cleverboi @FandaSin @BrodieOnLinux @neal as for #i386 I understood why cuz it was more and more painful m, but the problem with #i486 is that in several #embedded and #industrial setups there are still newly deloyed systems based off it.
I.e. #Vortex86 #SoC's cuz #MSDOS and shit still gets used in #industrial equipment.
Linux stopped supporting i386 with versions 3.4.99 (longterm)
& 3.6.9
respectably.
i386
where none of the toolchain (#musl) and utilities (#toybox) supoort it, i486
is still supported there.And I really want to continue developing a minimalist "rescue" distro that can handle such legacy hardware because it may be the only option to ddrescue
stuff from certain systems or to properly & reproduceably backup & restore them!
@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!
That being said @w84death 's #Floppinux v0.2.1 just booted through fine, so yeah, perfectly feasible as "low end testbed" unless I get like a #VIA #C3 / #C5 / #C7 or one of those expensive #Vortex86-made #486SX clones that @rasteri used for the #WeeCee, tho I'm shure noone would go below a #RaspberryPi #Pi0 / #Pi0W v1.3 or the original #PiModelB v1.2 in terms of #FrugalComputing.