“Intel announced yesterday that its upcoming low-cost/low-power CPUs code-named Silverthorne and Diamondville will be sold under a single brand once the products launch. The MID-centric product family will hereafter be known as ‘Atom’. Consumers are obviously meant to associate the Atom brand with objects of very small size, though Intel “Quark” would have a certain ring to it.”
…this is nice. Android running on Atom would be spectacular. If they ever designed a compact cellphone with those 2, it would be an instant best-seller. Whoever combines x86-compatibility in a portable format is King.
Atom won’t fit in a cell phone and Android doesn’t get any advantage from x86 since all the apps are written in Java.
Who would want a processor named after a Ferengi?
On first reading, the label “Atom Inside” sounded more like just stating the obvious.
I’d suggest there are quite a few “atoms” inside…
Who wants an Intel processor anyways. This looks like it was written by a Junior executive of Microsoft who wants to increase computer sales and there by increase Vista licensing agreement sales. AMD is a better value. AMD is being put on more and more servers and is also on many desktops and laptops.
No, no they’re not. AMD is loosing market share rapidly, and they’re dying so fast, that the community is worried they might bail, leaving us only with Intel. As someone who has only ever purchased Intel chips, I can say that if AMD drops out, it will suck for the consumers.
Why should current x86_64 CPUs intended for embedded devices support running MS-DOS directly? Or Windows XP 32 for that matter.
Build Long-Mode-Only CPUs and get rid of tons of silicon. They will certainly be much(a bit) easier tho scale down then. In the end, it could even run MS-DOS in BOCHS or QEMU if you are into that sort of thing. It’s not like bussinesses will replace their remaining Windows 3.11 “Servers” with an iPod.
As far as I can understand it there’s actually very little overhead in supporting 8086/88 inside a modern x86 core. In most designs the x86 opcodes are translated into various core specific micro ops. 16 bit operations are still supported in 32bit mode with the 0x66/0x67 prefixes and the MMU takes care of 8086 style addressing (more accurately the CPU is set up in such a way that an 8086 task has a memory map conducive to its execution but it isn’t seeing a physical chunk of memory but a chunk of memory mapped using similar techniques as are used for paging). It could be removed but the first thing that must happen is that the BIOS and boot block loaders of x86 OS’s must be changed to not use any 16bit 8086 code. These machines still boot in something resembling 8086 mode.
The long and the short of it is that you might save some silicon but fractions of a percent at best with no performance increase.