7,647 karma · joined November 25, 2013
They weren't trying to steal IBM's design, they already had one of their own, what they wanted to know was "is there any as yet unannounced functionality in the IBM VGA chip?" they didn't want to be caught out when some unknown registers popped up. Of course it turned out there was as yet unannounced functionality - but not by IBM's design, more because of the orthogonality of the design - MODE-X was discovered and became the basis for DOOM's speed, anyone who didn't support it lost out
TCP/IP won (IMHO) because the implementation was open source, and because no one was going to make a buck by locking others out (or charging them for the right to build an implementation). Plus there was a working reference implementation available for the taking
A true capability architecture needs separate register files for pointers and data with protections enforced when the address registers are loaded/stored, it's a step away from our models of linear address spaces that many of the languages we use today are based on. And any new CPU that requires everyone to learn a new language is probably a non-starter as a mainstream CPU
What ate them up was "what can you fit all on a chip with not many pins", followed by "what can you fit along with a cache on a chip with more pins", things move so much faster if everything's on the same die.
Tagged architectures are old, Burroughs mainframes had them back in the 70s along with rudimentary hardware objects (pageable even)
You make do with the memory and cycles available, things get easier as the resources get less tight, it's easy to use things like garbage collection rather than doing the hard yards and managing memory yourself, or to break branch prediction by using virtual objects
Our standard agreement for porting Unix to new hardware (we did something like 150 different boxes, not just macs) required a minimal ROM monitor that could download code from a serial port (we could provide source), we'd take it from there, write S/A code to store data on the harddrive, download a file system, start downloading kernels into ram debugging the disk and serial drivers until we got a shell prompt ... then moving development onto the box
The later MacOS running on A/UX ran in a single A/UX (system V) process
(do this with care, an entire pack is hundreds of volts)
The original was written by Bunnie Huang (a name to be sneezed at in his own right) who (I assume) grew up speaking Mandarin at home. Naomi is a local though and probably has broader local knowledge.
The original Shenzhen markets are still there (I've been going for a decade or so, they haven't changed that much), they're getting a bit crowded out by consumer electronics - I can still go and buy great tools in HQB at same places I was 10 years ago, reels of resistors at the same places, people will still sell you cut tape from part reels on the street - the big change are the electric bikes, you take your life in your hand each time you turn around :-)
x: mov -(pc), -(pc)
reads an instruction from x, increments the PC to x+2, then decrements the PC back to x and reads the same instruction, then decrements it again to x-2 and writes it, then it executes from x-2 ......
I also worked on the original A/UX port for the Mac II, some hardware (like the IWM) required tiny buzzy loops, we ran into one bug where using the floppy caused ADB to freeze, but only on the release machines, not the prototypes all our engineers had, turned out there was hardware that made access to the VIA faster by pulling the clock in for 1 cycle, if you sat in a loop reading the timer in the via to measure a sector time for the IWM in too tight a loop it upped the output clock from the VIA to the ADB chip and over clocked it ....