Would be a fun surprise if the 386 had its own Halt and Catch Fire mode.
https://www.rcollins.org/ddj/Jan97/Jan97.html
>On the standard Intel 80386 DX, asserting the undocumented pin at location B6 will cause the microprocessor to halt emulation and enter ICE mode.
[this is written from an ICE perspective - for "emulation", read "normal operation"]
This mode was introduced in the 80286, but I don't think the pins were exposed except in the special bond-out variant for ICE, and maybe early samples. You can trigger it in software (opcode 0F 04 on the 286, or by enabling a bit in DR7 on the 386), but then the processor disconnects from the bus and you have to reset it.
On the 286, you can get it to dump some otherwise hidden internal state, by using a prefix that no longer exists on 386s: https://rep-lodsb.mataroa.blog/blog/intel-286-secrets-ice-mo...
But the byte enable pins also implicitly communicate size, which would otherwise require another two pins. So this byte enable scheme breaks even (at least for chips with 16bit or 32bit buses).
The main goal is simplify the design of the motherboard.
<input name="layer" type="radio" onclick="show('https://static.righto.com/images/386-package/layer0.jpg')" id="layer1">
<label for="layer1">Pins</label>
then it would be possible to click the label name (i.e. Pins, I/O Vcc, etc.) instead of having to click the small radio circles.It's a small thing, but I think it's a lot more fun/easy/fast to click the different label names rather than the circles. It's truly a small nit - just in case it's an easy fix for you. Cheers!
(just to make sure: you need to add a unique "id" attribute for each "input", and then make a <label> tag for each label referencing that id in the "for")
Nesting the <input> inside the <label> is simpler. Then you don't need the id and for attributes. I think it avoids an unclickable space between them too.
For example, I know that thermal samples for the Pentium 5-era Xeon (Jayhawk) were produced, but I'd always wondered Intel went from the dummy to realizing "oh, shit, this is going to be way too hot in the long run."
8MB of DRAM, a 250MB spinning disk hard drive, 5.25 and 3.5 inch floppy bays, removable bios that I had to sort through a tupperware of chips to find the correct unit, some unnamed AGP video card that I had to slot removable chips into as well and a great big 16" CRT.
I think I had to install a special serial card in an ISA slot to use a mouse too.
Do you mean VGA rather than AGP? AGP came much later than the 386 and wouldn’t have been supported by its motherboard chipsets.
I can’t remember if those were available on 386s or started in the 486 era.
Full ISA connector (potentially missing the bit in the middle) and then a further piece? VLB
Shorter than ISA but higher density? AGP (it's even a bit shorter than PCI)
Was it at least a Pentium? Can't be AGP otherwise.
Going to ignore PCI-X, PCIE and obscure AGP variants
Back in the day - late 80s, very early 90s - I’d see Amstrad (ugh!) 286-based desktop systems on sale in our local branch of Dixon that included graphics cards fitted with VGA chipsets, but cards compatible with the AGP interface on then newer motherboards didn’t cross my radar until the second half of the 90s.
This one? https://en.wikipedia.org/wiki/Micro_Channel_architecture
Anyways.. this is what I really like about kens work.. the accidental discovery of beautiful structures while trying to answer abstract questions. Thanks for doing all this!
and Cyrix 486DLC hijacks 7 of those :)
A20M# (F13) - when supported by motherboard you can L1 cache whole ram instead of leaving first 64KB uncached
FLUSH# (E13) - when supported by motherboard you dont have to use hacks and flush L1 on every DMA access. Hacks (BARB mode) seemed clever at the time until everyone had a Sound Blaster DMAing audio constantly invalidating cache while gaming.
RPLSET (C6) RPLVAl (C7)- L1 cache status debug outputs
SUSP# (A4) SUSPA# (B4)- suspend support, wakes on INT and NMI. Good for laptops.
>The surprising thing is that one of the No Connect pads does have the bond wire in place
Somehow Cyrix picked this particular pin (B12) for KEN# input (enable L1 cache) :O
>From the circuitry on the die, this pin appears to be an output
Meaning the _one_ NC pin Intel CPU actually wires, an output no less, Cyrix demands driven low to enable cache.
Pedantic note: I think "quadratically" makes more sense here: we're talking about two dimensions.
At the time, Intel was primarily a memory manufacturer, and they had vertically integrated the complete workflow for anything that could fit into a 16-pin DIP. Anything that didn't, required them to outsource testing and packaging, or purchase expensive new machines. When CPUs were still being pushed against the wishes of upper management ("A computer has only one CPU but lots of memory chips, so the memory is a better business"), it was a hard sell to invest lots of money for an uncertain market.
kens•6mo ago
OptionOfT•6mo ago
loa_in_•6mo ago
kens•6mo ago
wkat4242•6mo ago
johnklos•6mo ago
Since the bond wires are just hanging out in air, does this mean that a chip like this could be ruined by dropping it which might cause the bond wires to move enough to short something?
Thanks for all your hard work!
userbinator•6mo ago
generuso•6mo ago
This failure mode is quite low on the list among others, but it is something that people did investigate. For example: "Swing Touch Risk Assessment of Bonding Wires in High-Density Package Under Mechanical Shock Condition" https://asmedigitalcollection.asme.org/electronicpackaging/a...
besserwisser•6mo ago
imoverclocked•6mo ago
kens•6mo ago
TZubiri•6mo ago
kens•6mo ago
bunabhucan•6mo ago
rts_cts•6mo ago
s1110•6mo ago
userbinator•6mo ago
danparsonson•6mo ago
pyuser583•6mo ago
mannycalavera42•6mo ago
Loughla•6mo ago
vodkadin•6mo ago
tjwebbnorfolk•6mo ago
mavamaarten•6mo ago
kkaske•6mo ago
s1110•6mo ago
I mean I eventually read the article. Sorry for that. But we're at "Hacker News", sporting hackers ethics, aren't we?
inferiorhuman•6mo ago
pyuser583•6mo ago
wood_spirit•6mo ago
drysine•6mo ago
red75prime•6mo ago
astrange•6mo ago
That and financial businesses usually don't operate outside their host country anyway. Though you do want your customers to see their accounts when they're traveling.
pyuser583•6mo ago
In all fairness, this isn’t a good use of that technique. But most websites are of no interest outside a handful of countries.
orbital-decay•6mo ago
tgv•6mo ago
justsomehnguy•6mo ago
> kens on April 10, 2022
> Are you trying to access from Russia? Russia is currently blocked.
https://news.ycombinator.com/item?id=30974444
> kens on Dec 3, 2022
> Unfortunately there are also many people in Ukraine who didn't personally do anything to deserve what's happening. Consider the country filter a small reminder of the ongoing war and a suggestion that you might find better opportunities outside Russia.
https://news.ycombinator.com/item?id=33846782
Yet he doesn't consider to 'find better opportunities outside of the USA' despite the actions of the USA government in the last 30 years.
grishka•6mo ago
Ken himself did block access to his website from Russia for a while after 24/02/2022, but right now it loads for me after a CF captcha.
rylando•6mo ago
kens•6mo ago
rylando•6mo ago
Thanks for the info, how interesting!
(for those who don’t know, mAs = mA • seconds = milliampere seconds. It’s how Radiographers measure how much x-ray photos are being produced by the tungsten filament in an X-ray tube. kVp is kiloVoltage potential and it’s how we measure the speed and thus the penetration power of the X-rays. 130kvp is slightly more than the 120kvp used for an avg human chest radiograph)
fecal_henge•6mo ago
kens•5mo ago
The scan was performed on our Neptune Microfocus scanner, configured with a 130 kV source. Current varies on this source depending on scan settings; in this case 123 µA. Each voxel in this scan is 12.8 microns; for smaller parts that we're able to move even closer to the X-ray source we can achieve 3-6 micron voxels.
Compared to medical CT scans, this is much higher resolution--medical CT scans have voxels on the order of 0.5 to 1 mm! This is possible because we're able to apply much higher X-ray doses in industrial scans. Medical CT scans are typically on the order of 120 kV, at higher current but for much less time--perhaps a few seconds compared with minutes to hours for an industrial CT scan.