6 ms·
What is old is new again - this is the architecture of the Amiga! And before that the C=64 and the Atari 800.
by gaius 10y ago
What is old is new again - this is the architecture of the Amiga! And before that the C=64 and the Atari 800.
- untilHellbanned 10y agoWhy was it a non-starter for Intel and what made Apple use it? I'm curious because I don't know about computer architecture.
- neppo 10y agoApple has control over the chip and the OS, whereas Intel only makes the chip
- gaius 10y agoAgain that is how it was back in the day, CPU and supporting hardware, OS, compiler, standard libs etc all co-engineered. Tho' in the case of the Amiga the CPU was part of the supporting hardware, the heart of the system was something else that farmed work out to the CPU or a co-pro as appropriate...
- walterbell 10y agoIs there a good online reference for this design?
- gaius 10y agoThere is an excellent book https://www.amazon.co.uk/Future-Was-Here-Commodore-Platform-ebook/dp/B007V5BVJG/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=1474733494&sr=8-1 https://www.amazon.co.uk/Future-Was-Here-Commodore-Platform-... http://bogost.com/writing/blog/the_future_was_here/ http://bogost.com/writing/blog/the_future_was_here/
- _ph_ 10y agoIntel seems to be captured in its own x86 world. There were no big changes to the instruction set for ages, even the x64 extensions were designed by AMD. So while Intel still excels at manufacturing, the few projects for breaking out of their box failed (Ithanium, Larrabee). And also: why are there no Intel chips yet who include all the nice things USB-C can offer to the market? E.g. Thunderbolt, newest DisplayPort.
- qznc 10y agoIntel added for example: FMA (3) with Haswell in 2013 https://en.wikipedia.org/wiki/Multiply%E2%80%93accumulate_operation#Fused_multiply.E2.80.93add https://en.wikipedia.org/wiki/Multiply%E2%80%93accumulate_op... SSE4.2 with Nehalem in 2008 https://en.wikipedia.org/wiki/Nehalem_(microarchitecture) https://en.wikipedia.org/wiki/Nehalem_(microarchitecture) AES in 2008 https://en.wikipedia.org/wiki/AES_instruction_set https://en.wikipedia.org/wiki/AES_instruction_set SHA in 2013 https://en.wikipedia.org/wiki/Intel_SHA_extensions https://en.wikipedia.org/wiki/Intel_SHA_extensions
- MrBuddyCasino 10y agoIntel even added customer specific logic to its server class CPUs, which are only usable by them to speed up certain operations: https://news.ycombinator.com/item?id=11875255 https://news.ycombinator.com/item?id=11875255
- userbinator 10y agoThat seems more like a vague rumour than anything, at least until someone leaks some more info. (That it hasn't occurred, makes me somewhat doubting. Maybe the various undocumented instructions which have been found over the years are part of this...)
- gaius 10y agoThis approach was common in mainframes - you would buy a box that contained everything, but only the parts that you'd paid for would be accessible. If you wanted more, you could just apply an unlock code that you'd bought, and new features would come online, that were lying dormant all along. Even up to the level of more CPUs.
- bluedino 10y agoApple used Motorola because they were cheap compared to intel
- mattnewton 10y agoBecause intel said no originally; they didn't think there would be the volume to justify the expense of a custom chip at the price apple was willing to pay. http://m.imore.com/intels-outgoing-ceo-explains-how-they-turned-down-original-iphone http://m.imore.com/intels-outgoing-ceo-explains-how-they-tur...
- headShrinker 10y agoOne important aspect to apple's position is it had a new set of limitations other processor designers weren't dealing with; power consumption and size. Yes there were small processors and there were processors that didn't use tons of power, but they weren't fast. Apple had a very specific set of needs and apple being apple, was able to completely costomize its design and supply chain
- mattnewton 10y agoMy speculation: Intel doesn't want to threaten it's core buisiness in the pc market (which is heavily dependent on backwards compatibility), and the experience with itanium in the hpc market probably left a bad taste in their mouth.
- nickpsecurity 10y agoSame thing I was going to say. Amiga architecture was apparently the one of the future rather than past. Too ahead. In parallel, though, we also saw mainframes use a similar trick. Their usage was more narrow, though.
- wolfgke 10y ago> Amiga architecture was apparently the one of the future rather than past. Too ahead. I wouldn't call an architecture this way if it proves very difficult to extend without strongly breaking compatibility.
- nickpsecurity 10y agoIt's worth consideration although I don't think an architecture requires backward compatibility by definition: more a way to keep users or earnings reliably. You'd be saying that Mac OS 9 isn't an architecture since Mac OS X was different. Or PS2 -> PS3 mismatch meant they weren't architectural designs. Android API isn't backward compatible with GNOME or KDE on Linux. I'm just not seeing a lack of B.C. meaning there's no architecture or platform. If it was, though, we might potentially resolve the issue if there's a standard API for various things where the implementation can be ignored (and improved w/ SW or HW). Modern example of an Amiga-like architecture might be Microsoft's DirectX techs where there's API's for networking, I/O, audio, and video. Any of those might have been accelerated with dedicated coprocessors with apps looking the same. At least one or two were in practice. Likewise, the programming model might obviate the need for this consideration. One where they were tasks called as needed by a control code w/ optional acceleration might mean just the control code or OS interface needs to change per release or platform.