4 ms·
To think that support for something so edge-case has been supported this long is remarkable. Even very basic embedded x86 processors are 80486 caliber. Those m
by astrodust 14y ago
To think that support for something so edge-case has been supported this long is remarkable.
Even very basic embedded x86 processors are 80486 caliber. Those more feeble than that have no hope of running the current kernel in any meaningful fashion.
- asveikau 14y agoIn 2000, someone gave me a 386 desktop that they were about to throw out, and I ran OpenBSD on it until 2005 or so. (I was a student, so getting new hardware was more of a big deal then.) To get it working I had to recompile the kernel (which I did on a "more capable" Celeron 366) without support for newfangled hardware such as USB and PCI in order to have enough memory to boot and log in in a tolerable amount of time. (Otherwise too painful due to swap.) So I was pretty grateful at the time that it was still working, even though what I was doing was, now I can say with the benefit of hindsight, pretty crazy.
- enneff 14y agoI ran a diskless 386DX 33mhz in my bedroom for many years, because it didn't make any noise. It ran a cut-down Linux distribution based on slackware, and I used it as a terminal and for small programming tasks. I also kept it around for sentimental reasons, as it was the machine I did most of my early coding on. It didn't feel right to throw it out. So thanks, Linux, for supporting my old junk hardware as long as you did! And congrats on losing ~400 lines of crufty code.
- SoftwareMaven 14y agoI loved my Celeron. I had a 300 which over clocked amazingly well to 450Mhz. In fact, those were the last days of my "dinking" with hardware. The Pentium and beyond offered such diminishing rewards that it wasn't worth it.
- dspillett 14y agoCelerons of that era were very easy to officially overclock generally because a great many of them were underclocked by Intel. They ended up with far more of the more expensive 400+MHz capable parts than they expected to produce (presumably they were overly cautious when predicting how well the production process would work and therefor how many of the better rates chips thye'd get) but too few of the cheaper 300Mhz and 333MHz rated parts that were actually selling well - so they rebadged faster units as slower ones to fufil sales promises for the slower units. This meant buying a machine based around a Celeron 300 or 333 (often referred to as "Silly-rons" at the time) was a lottery: you might have got one that is genuaninely expected not to be stable if run much faster, or you might have got one that Intel could have sold as a 450+MHz device.
- ableal 14y agoAs a side effect, those chips also helped launch Internet publishing - sites like the improbable Toms's Hardware, founded by a German M.D. if memory serves, cut their teeth on overclocking advice and benchmarks.
- astrodust 14y agoIt wasn't so much as they were underclocked, but that Intel's process was so refined that they were often produced over-spec. The other thing that made them so easy to over-clock was that, unlike the Pentium Pro, II and III, there was no on-chip L2 cache that would malfunction at higher speeds. All you were over-clocking was the CPU. I had a dual-Celeron system that ran like a champ for the better part of ten years.
- Klinky 14y agoThe binning process where higher end CPUs are marketed as lower end parts has been going on forever. Only the first generation Celerons (which everyone hated) had no L2 cache. The second generation had 128KB of full-speed on-chip cache, which is actually why it overclocked well. The Pentium II and early Pentium III had 512KB of half-speed off-chip cache which struggled to keep up with the CPU when overclocking.
- bryanlarsen 14y agoCurrent Sandy Bridge & Ivy Bridge "K" chips also overclock very easily (you can add more than 1 ghz to the max speed).
- Natsu 14y agoI still have an 8088 with a color display, dot matrix printer, math coprocessor, maxed out RAM (64 KB? I don't even remember) and a 10 MB hard drive + dual disk drives. I should see if it actually boots someday....
- dalke 14y ago640KB was the max RAM. My first PC was the same configuration, except I had a 32MB drive. Oh! And towards the end I had both a CGA and Hercules card so I could have two screens.
- huxley 14y agoPCs released after the XT could be configured with up to 640KB but the original IBM PC was limited to a max of 256KB (entry level config was 64KB).
- yuhong 14y agoOn the motherboard. You could still add RAM using ISA cards.
- dalke 14y agoTo confirm, http://www.pcworld.com/article/237878/can_you_do_real_work_with_the_30_year_old_ibm_5150_.html http://www.pcworld.com/article/237878/can_you_do_real_work_w... shows a model 5150 (it's the only model with a cassette port on the back) which has 640K of RAM.
- dalke 14y agoIt looks like the model 5150 didn't come with a hard disk, and the only official support for that was through the IBM 5161 Expansion Chassis. I think the author would have commented having an external drive for a PC, so I think it's safe to assume at least an XT equivalent. (I've been searching for images of the chassis but to no success. I've never seen one, nor heard of it before today.) And in the other direction, a PC Jr (also an 8088) maxed out at 128 KB, according to my references, though Wikipedia says there were third-party extensions to 736K. In any case, the Jr doesn't support the 8087 math coprocessor, so that's not what the author has.
- petercooper 14y agoTangential trivia: MRI Ruby still has compiler directives and, supposedly, support for the Atari ST. Always weird bumping into them when going around the codebase. No idea if it actually works or why it's even a thing.
- mahmud 14y agoGNU CLISP, an small portable Common Lisp implementation supports Acorn RISC OS, NeXT, Amiga and OS/2. http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/ http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/
- robin_reala 14y agoRISC OS is still going (they just released a Raspberry Pi build) and OS/2 morphed into the commercial eComStation that is actively maintained. NeXT is dead though and Amiga fractured.
- ynniv 14y agoNeXT is dead Didn't you get the memo?
- robin_reala 14y agoOK, fair point :)
- pdw 14y agoSupport is a bit exaggerated, the 386 option hasn't compiled since the 3.2 release due to unconditional use of 486-only instructions (https://bugzilla.kernel.org/show_bug.cgi?id=44931 https://bugzilla.kernel.org/show_bug.cgi?id=44931). Who knows if it actually worked before that.
- lmm 14y agoIt was working in '07; I gave up maintaining that system when glibc went 486-only.