Slashdot Mirror


Intel Threatens To Revoke AMD's x86 License

theraindog writes "AMD's former manufacturing division opened for business last week as GlobalFoundries, but the spin-off may run afoul of AMD's 2001 cross-licensing agreement with Intel. Indeed, Intel has formally accused AMD of violating the agreement, and threatened to terminate the company's licenses in 60 days if a resolution is not found. Intel contends that GlobalFoundries is not a subsidiary of AMD, and thus is not covered by the licensing agreement. AMD has fired back, insisting that it has done nothing wrong, and that Intel's threat constitutes a violation of the deal. At stake is not only AMD's ability to build processors that use Intel's x86 technology, but also Intel's ability to use AMD's x86-64 tech in its CPUs."

118 of 476 comments (clear)

  1. if they do that by bugs2squash · · Score: 2, Insightful

    It's the end of the x86 dominance. People will just look harder to find alternatives.

    --
    Nullius in verba
    1. Re:if they do that by Anonymous Coward · · Score: 5, Insightful

      Bah hah hah, silly idealist.

      The two-party system is here to stay in American politics and the x86 stranglehold.

    2. Re:if they do that by mdm-adph · · Score: 5, Funny

      I, for one, welcome our new strong ARM'd overlords.

      --
      It is by my will alone my thoughts acquire motion; it is by the juice of the coffee bean that the thoughts acquire speed
    3. Re:if they do that by hwyhobo · · Score: 4, Insightful

      People will just look harder to find alternatives

      People who? Do you really think that 99% of the computer users even know what x86 means?

      --
      End anonymous moderation and posting on /.
    4. Re:if they do that by ORBAT · · Score: 2, Funny

      Yeah. And it's the Year of the Linux Desktop(tm) too, right?

    5. Re:if they do that by ADRA · · Score: 4, Insightful

      -They- being the PC manufacturers that sell most PC's these days. -They- being the OS vendors who would be into a world of hurt trying to support every differing configuration of the x86+ based architectures....

      Since x86_64 is a superset of x86, would this mean AMD couldn't even sell x86_64 based chips either?

      --
      Bye!
    6. Re:if they do that by the+linux+geek · · Score: 5, Insightful

      If x86 dies, which it is in the process of doing, Microsoft will port Windows to run on SPARC, ARM, PPC, whatever comes next. Microsoft has gotten where it is by being good at business, and being good at business does not consist of pushing a dying platform that it has no vested interested in. Windows has been ported to other architectures before, and is inherently portable.

    7. Re:if they do that by nametaken · · Score: 4, Insightful

      I heard this argument when it was "people will stop using windows".

      It's nice to think about and all, but wake me up when it actually happens.

    8. Re:if they do that by SIR_Taco · · Score: 5, Informative

      Since x86_64 is a superset of x86, would this mean AMD couldn't even sell x86_64 based chips either?

      Funny thing is that AMD licensed/agreed to share their x86_64 arch back to Intel.
      So essentially it's:

      "I'll let you play with mine if I can play with yours."

      Now a 3rd party (loosely affiliated with AMD) is playing with Intel's x86, and that wasn't part of the agreement.

      --
      I say don't drink and drive, you might spill your drink. Before you get behind the wheel just stop and think.
    9. Re:if they do that by DragonWriter · · Score: 2, Informative

      People who? Do you really think that 99% of the computer users even know what x86 means?

      No, but most users don't need to. Microsoft does, and Microsoft has no reason to want any one other firm to be indispensable to PC vendors the way Microsoft is. So, if the AMD cross-licensing agreement goes away and there isn't serious competition for Intel in the x86 world, I'd expect Microsoft to start supporting alternatives.

    10. Re:if they do that by ciroknight · · Score: 5, Insightful

      Yes. You said it yourself: x86-64 is a superset of x86; the architecture is reliant on instructions from the legacy set. No license to the legacy set, no dice on building the superset.

      But that's okay, because there's no way Intel would ever pull the trigger. This is just corporate posturing to get a better crosslicensing agreement and a slice of the Foundry's pie. They'll fight it out for a couple more weeks and then a "settlement" will be reached behind some closed doors, probably with the Foundry agreeing not to mint over N non-x86 chips and some cash changing hands in whichever direction.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    11. Re:if they do that by bucky0 · · Score: 3, Interesting

      But the big draw of windows is the inertia of 1,000,000 one-off apps that businesses have written. Microsoft would be scared of people moving to another architecture just because if people were making a (painful) switch anyway, they might look at the alternatives.

      --

      -Bucky
    12. Re:if they do that by Tiber · · Score: 5, Insightful

      HAHAHAHA.

      I'm on my way to buy SUN stock right now.

      Oops, maybe not.

      OK, I'm off to buy stock in HP!

      Errr...

      I'm going to purchase some DEC stock!

      Oh fooey.

    13. Re:if they do that by arth1 · · Score: 2, Insightful

      Windows is inherently portable? Thus speaks someone who hasn't tried switching the motherboard and CPU between Intel and AMD on a HP box, and watched Windows failing to boot because the OEM only included a HAL library for one of them.

      Yes, there were Alpha and MIPS versions of Windows NT. No, there haven't been any for a long, long time. If it was just a matter of passing a different CPU flag at the top level of the compiler, it would have cost MS next to nothing to continue to provide support for XP, Vista and W7. Windows has become quite married to x86 over the years, and I doubt that switching would be trivial.

      And, of course, it wouldn't do much good if Windows would run on a different CPU, if all the apps which people run aren't also recompiled for the new CPU. Windows binaries aren't exactly p-code...

    14. Re:if they do that by fuzzyfuzzyfungus · · Score: 2, Informative

      The trouble isn't porting Windows; but in dragging all the x86 legacy stuff with it. With the exception of a modest amount of .NET CLR stuff, which should actually be platform agnostic, virtually all of the windows ecosystem is on x86. And, as is mentioned every single time linux migration is discussed, most of that is never, ever, ever going to get ported. Obsolete software from dead companies, in house stuff, old versions that are uneconomic to upgrade, etc. Not to mention drivers.

    15. Re:if they do that by jjrockman · · Score: 4, Funny

      "I'll let you play with mine if I can play with yours."

      Man, if I had a nickel...

      --
      Quit jabbering on the phone while driving. You are not that important.
    16. Re:if they do that by Anonymous Coward · · Score: 5, Funny

      sounds RISCy.

    17. Re:if they do that by MightyYar · · Score: 2, Insightful

      Windows is not the issue... the millions of x86-dependent applications would be the issue. This isn't Linux where you just apt-get the version for your architecture.

      They'd have to do something in emulation like Apple did with Rosetta, but then the non-x86 version of Windows would run most applications slowly and so PC magazine and consumer reports and your friendly neighborhood geek would recommend sticking with x86, since MS doesn't have Apple's option of simply making the old architecture go away.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    18. Re:if they do that by the+linux+geek · · Score: 4, Insightful

      Windows is still maintained on Itanium; both it and the Alpha port could run x86 binaries at close to native (or, at one point in the Alpha's lifetime, faster.) I'm no Microsoft fanboy, but I don't think they're stupid.

    19. Re:if they do that by neokushan · · Score: 2, Funny

      CELLebrate good times, come on!

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    20. Re:if they do that by Daravon · · Score: 4, Funny

      Windows on PPC... Then Microsoft will tout how much faster PPC is than x86 based processors, and the world ends in an infinite loop.

      --
      I traded all my mod points for these magic beans.
    21. Re:if they do that by Anonymous Coward · · Score: 5, Informative

      If it was just a matter of passing a different CPU flag at the top level of the compiler, it would have cost MS next to nothing to continue to provide support for XP, Vista and W7. Windows has become quite married to x86 over the years, and I doubt that switching would be trivial.

      It IS just a matter of passing a different CPU flag. MS discontinued the MIPS, PPC, and Alpha versions because there was not only no demand for it, but the few people who bought it tied up lots of MS customer service time bitching that X86 programs didn't run on MIPs/PPC/Alpha.

      Windows is no more married to X86 than Linux or OS X. In fact, I can tell you where to get a fairly modern Windows Kernel running on a PPC chip in pretty much any electronics store: The XBox 360.

      The NT kernel was designed from the ground up to be portable. The only real reason it's currently only supporting X86 is because that's the only place there's any sort of demand. If X86 dies (And it won't. AMD and Intel both have lots to lose, though AMD more than Intel here), Microsoft will port over to PPC (Or whatever), throw on an emulation layer, and probably take the opportunity to break a whole bunch of crappy stuff in Windows that's maintained simply for backwards compatibility.

    22. Re:if they do that by nurb432 · · Score: 2, Insightful

      Just like apple was in a world of hurt when they dropped the more elegant PowerPC for ix86?

      Yup, really killed them off didn't it.

      ( I still think it was a bad move, but no sense harping on it now.. )

      A complete change over would allow a more controlled HAL standard to be developed too.

      --
      ---- Booth was a patriot ----
    23. Re:if they do that by Yvan256 · · Score: 3, Interesting

      Funny that you should say that, because if the world ends at the infinite loop, we'll all be running Mac OS X.

    24. Re:if they do that by Fulcrum+of+Evil · · Score: 3, Insightful

      We have virtualization now - If I can run a legacy app in a dos box, who cares what the actual hardware is?

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    25. Re:if they do that by Grave · · Score: 5, Insightful

      Intel has no intention of preventing AMD from making x86 chips, because they know they'll be unable to manufacture any of their own chips as well (with x86-64 licensing coming from AMD). This is purely meant to ensure that anybody who might come along and acquire the foundry business doesn't wind up trying to produce their own x86 chips. Or at least, I'd like to believe such...truthfully, I wouldn't put it past Intel to just be making a money grab here.

      Either way, holding AMD in violation of their agreement means they would effectively forfeit 64-bit licensing rights as well, and that makes no sense for them.

    26. Re:if they do that by LandDolphin · · Score: 2, Insightful
      I don't normally do the "Mod Parent Up" comments, but this really deserves it.

      But that's okay, because there's no way Intel would ever pull the trigger. This is just corporate posturing to get a better crosslicensing agreement and a slice of the Foundry's pie. They'll fight it out for a couple more weeks and then a "settlement" will be reached behind some closed doors, probably with the Foundry agreeing not to mint over N non-x86 chips and some cash changing hands in whichever direction.

      That pretty much sums it all up. Grandstanding.

      --
      Spelling and Grammar errors have been added to this post for your enjoyment
    27. Re:if they do that by SebaSOFT · · Score: 3, Informative

      Agree, ARM has been gaining grounds due to it's low (as none) power consumption when idle. So long backward compatibility tough.

    28. Re:if they do that by MrCrassic · · Score: 2, Informative
      You're dreaming.

      Intel has 18-wheeler-truckloads more resources for marketing than AMD will ever hope to garner. While there will always be the minority that will seek alternatives, Intel has the power to win them over, whether it'd be through financial incentives, equipment "giveaways" or brute-force, corporate style.

      If AMD loses its x86 license, I'll speculate that AMD will have to choose the three obvious paths:
      • 1. Sell itself to Intel, thus unilaterally giving Intel ~100% control over mainstream consumer microprocessor fabrication, production and sales, OR
      • 2. Throw lots of money and time into developing a new processor spec (which will take forever and has a high risk of failure), OR
      • 3. Use an older or less popular spec (The resurrection of PowerPC?).

      I don't want to see AMD go down, but it's kind of sad to know that Intel has the power to do exactly that.

    29. Re:if they do that by Anonymous Coward · · Score: 5, Funny

      You'd probably swallow it by accident.

    30. Re:if they do that by Anonymous Coward · · Score: 3, Funny

      99% is a really high target man. I doubt that 99% of computer users know where the power switch is.

      Maybe you should look to 5% or 10%

    31. Re:if they do that by NotBornYesterday · · Score: 2, Informative

      It also seems a bit unclear as to why Sun continue to develop and produce the SPARC

      Because there is a demand for it, and it does things that x86 doesn't. 8 cores * 8 threads = awesome virtualization abilities. The ability for SPARCs to scale up in a linear fashion to > 100 cores in a single general-purpose SMP box positions it in the high-end datacenter realm, where PPC is, but not x86. Plus, SUN isn't going it alone. Fujitsu is on the SPARC bandwagon with them.

      --
      I prefer rogues to imbeciles because they sometimes take a rest.
    32. Re:if they do that by coopaq · · Score: 4, Funny

      The two-party system is here to stay in American politics and the x86 stranglehold.

      And operating systems and phone companies and potato chips and cereals and sexes.

    33. Re:if they do that by Darkness404 · · Score: 2, Interesting

      Yah, unfortunately for most things more advanced than DOS, it fails on anything that isn't currently top-of-the-line. Not to mention that ARM, SPARC, and PPC architectures simply aren't fast compared to x86. Sure, they are more power efficient, but I challenge you to find a single CPU (multi-cores are acceptable, multi-CPUs not) thats based on ARM, SPARC or the PPC architecture that is at least as fast as a low-end Core i7 and are cheap enough to be included in a mid-range PC.

      --
      Taxation is legalized theft, no more, no less.
    34. Re:if they do that by ADRA · · Score: 4, Insightful

      Virtualization makes the host arch less important, but we generally don't run a virtual instance of a different hardware platform. The reason is that there's a really high penalty of either recompiling (with the possibility of bugs) or full instruction emulation which makes runtime performance horrrrrrrible.

      Most modern virtualization systems will run the guest OS almost natively using CPU's virtualization extensions to make the magic happen without much overhead.

      Try running Windows on an ARM or PPC x86 emulator and see how long it takes before throwing your hands up in slowness frustration.

      --
      Bye!
    35. Re:if they do that by socsoc · · Score: 2, Insightful

      Microsoft has gotten where it is by being good at business, and being good at business does not consist of pushing a dying platform that it has no vested interested in.

      So now they just push a dying os that they have a vested interest in?

    36. Re:if they do that by EdwinBoyd · · Score: 5, Funny

      Don't blame me, I bought a Cyrix!

      Feel free to mock me, however.

    37. Re:if they do that by agw · · Score: 2, Informative

      If x86 dies, which it is in the process of doing, Microsoft will port Windows to run on SPARC, ARM, PPC, whatever comes next.

      You must be new. There already was a PPC port and a speculated Sparc port as well. That was, what, 10 years ago?

    38. Re:if they do that by TubeSteak · · Score: 5, Insightful

      But that's okay, because there's no way Intel would ever pull the trigger. This is just corporate posturing to get a better crosslicensing agreement and a slice of the Foundry's pie.

      RTFA carefully.
      By alleging that AMD is violating the agreement, Intel can pull the trigger on AMD and still use AMD's patents.
      Because of Intel's threat, AMD is saying that they can pull the trigger and still use Intel's patents.

      It's an interesting game of chicken that they're both playing.

      --
      [Fuck Beta]
      o0t!
    39. Re:if they do that by kasperd · · Score: 3, Insightful

      Since x86_64 is a superset of x86, would this mean AMD couldn't even sell x86_64 based chips either?

      Is it time for AMD to make some more steps in throwing out the heritage from x86? Yes an x86-64 CPU can run in backward compatible 16 and 32 bit modes. In fact they still start up in 16 bit mode from which they have to be switched to 32 and then 64 bit mode. But the 64 bit mode could have done more to remain backwards compatible with old 16 and 32 bit code, however at the time AMD made the bold decision to allow some old software to not work in the 64 bit mode. Maybe it is time to take another step in getting rid of the heritage. How about making it possible for the CPUs to start up directly in 64 bit mode? That would be a natural next step towards completely getting rid of the backward compatible modes. The 64 bit instruction set can hardly be called the same instruction set as the 32 and 16 bit ones, first of all it is 64 bits, and it also has more general purpose registers. Those are clear distinctions from the old instruction set, and it was created by AMD, so I don't think Intel could prevent them from using it. I know you can run 16 and 32 bit code in the 64 bit mode, and a lot of people still use it (at least the 32 bit code), but I still think we are at the point where the 64 bit AMD ISA is more important than the 32 bit Intel ISA.

      --

      Do you care about the security of your wireless mouse?
    40. Re:if they do that by turgid · · Score: 3, Insightful

      So, if the AMD cross-licensing agreement goes away and there isn't serious competition for Intel in the x86 world, I'd expect Microsoft to start supporting alternatives.

      Windows already ships by the million on PowerPC hardware: XBox 360.

      Before the XBox 360 came out, the development environment that Microsoft was supplying was Windows ported to Power Mac hardware (G5 I believe).

      AMD x86 processors aren't going away, though. This is intel just flexing its muscles, spreading FUD to get AMD's share price down and to scare consumers away from its chips.

      All of these big technology companies have patent cross-licensing deals with each other. You'd better believe that intel can't survive without AMD's patents, and AMD can't survive without intel's, or Sun's, HP's, Microsoft's, TI's, FreeScale's... and so on.

    41. Re:if they do that by hattig · · Score: 3, Interesting

      There's a lot at stake.

      It appears from the snippet of Intel-AMD agreement posted that I've seen (at Tech Report, in comments) that The Foundry Company is perfectly fine under the agreement, as AMD has a certain share of the company, and it formed from AMD's assets.

      So Intel might be playing with fire. They lose this, they've just lost x86-64 - and Itanium is dead due to minimal investment in the past 5 years, and this year is when 64-bit x86 will hit the common desktop with Windows 7. More likely that AMD would get that license really loosened if they won and a bunch of money, but you know, if they're backed by ballsy Arabs...

      If AMD lose, Intel could have all sorts of fun.

    42. Re:if they do that by KillerBob · · Score: 2, Interesting

      Even still, the question I'm wondering is if x86_64 uses licensed bits of x86 instructions in its specification. Because if that is the case, wouldn't that mean that Intel can theoretically have this also prohibited from use as well?

      Theoretically, yes. Practically, no. While it does develop on prior art, it also implements something new, and so it's considered new technology. It'd be like me trying to copyright the letter e, and then suing you for using the word "the".

      There's also no way that Intel would pull that trigger. Sure, they could stop AMD from producing chips which support x86. But they'd lose their rights to use x86-64. Seeing as so many of the computers in the world run Microsoft, that'd be corporate suicide: Microsoft, in its infinite wisdom, has deigned not to implement a 32-bit workaround to the 4GB memory addressing limit. As new computers are routinely being sold with 6GB or more RAM, they'd be writing themselves out of the market for future computer manufacture. While IA64 *is* a supported architecture in 64-bit Windows, nobody's developping for it since Intel decided to scrap the architecture and focus on building x86-64 CPU's. I'm not even sure it's on the supported list for Windows 7, to be honest...

      They'd also lose out on a significant chunk of the market, as it would take time for them to start designing and building IA64-based chips again, during which time AMD, which would still be able to use x86-64 in its chip design would be able to dominate the market.

      Yes, I'm oversimplifying the intricacies of CPU design. But it's easier to drop a part of your architecture that's really only there for backwards compatibility in the first place than it is to scrap an architecture completely and rework your existing technology to take advantage of an alternative so that your product can remain viable in the marketplace.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    43. Re:if they do that by Bert64 · · Score: 2, Funny

      It's mutually assured destruction, x86-64 has become ubiquitous enough now alongside x86 that neither side would be stupid enough. In fact, you would end up with VIA being the only manufacturer who has agreements with both parties and thus legally allowed to manufacture x86 compatible processors

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    44. Re:if they do that by doublebackslash · · Score: 3, Interesting

      I'd like to see this go a bit father.

      Today's chips, at their core, look a lot like RISC chips. They do a lot of work to hide that, translating x86 ops to native ops. I'd like to see a chip that can run in a x86 'translated' mode and a 'native' RISC mode, much like was done with 32bit/64 bit.
      this is, admittedly, a much harder task to accomplish, but exposing a more efficient RISC mode would drive OS vendors to migrate to that. With a bit of careful juggling and VM technology the chips would allow legacy code to run while exposing the more efficient native modes to software that took advantage of it.
      Such a shift would take time, but so is 64bit.

      Oh well, I guess I'll go back to the idea lab and keep on dreaming.

      --
      md5sum /boot/vmlinuz
      d41d8cd98f00b204e9800998ecf8427e /boot/vmlinuz
    45. Re:if they do that by hattig · · Score: 2, Insightful

      Every?

      Business apps are written in .NET, Visual BASIC and Java.

      Maintained applications would get recompiled - Microsoft would surely provide an easy means to compile to the new architecture! Apple managed it with far less resources. Twice.

      It would be a risk, but on a five year plan ... maybe not.

    46. Re:if they do that by irtza · · Score: 4, Funny

      as long as it doesn't SPARC an idea.

      --
      When all else fails, try.
    47. Re:if they do that by Bert64 · · Score: 2, Informative

      The Cell is PPC based, can be faster than a Core i7 in some respects and is available cheaply in quantity.
      If you are willing to order sufficient quantity, IBM can crank out fast and cheap PPC chips quite easily... They did it for both Sony and MS with their respective games consoles.

      Emulation on the other hand will always incur a performance hit, sometimes quite a substantial one... Tho it helps if the CPU is designed to handle it. When the Alpha was still fairly new, you could run x86 emulation on it and actually outperform the real x86 hardware that was available at the time, but unfortunately Alpha was never made in sufficient quantities to push the prices down.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    48. Re:if they do that by mmkkbb · · Score: 2, Insightful

      Why? Apple, Microsoft, and Sony (at the least) have all changed architectures without losing all binary backward compatibility.

      --
      -mkb
    49. Re:if they do that by Xtravar · · Score: 2, Informative

      Today's chips, at their core, look a lot like RISC chips. They do a lot of work to hide that, translating x86 ops to native ops. I'd like to see a chip that can run in a x86 'translated' mode and a 'native' RISC mode, much like was done with 32bit/64 bit.

      Except wouldn't that potentially be slower? More data would need loading off the disk into memory, and from memory into cache, since the RISC translation is (usually) larger.

      Don't get me wrong, there's a lot 'wrong' with IA32, but I'm not so sure it would be worth using a 100% RISC ISA as an alternative. Complex instructions can be beneficial.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    50. Re:if they do that by frieko · · Score: 4, Insightful

      Misconception. RISC may be more elegant but it is less efficient. Translation and register renaming take up tiny amounts of die compared to the instruction cache savings of x86.

    51. Re:if they do that by Darkness404 · · Score: 2, Interesting

      The Cell is PPC based, can be faster than a Core i7 in some respects and is available cheaply in quantity.

      Fast as in, will run desktop applications fast, or can do some obscure math calculations fast? Because, according to most reports, Core i7 architectures (or scaled down versions) will be what Intel is going to be pushing for the next few years, and in every report I have read, they totally demolish the competition (x86) in "real" speed. Whereas the Cell was more or less built to run supercomputers, render HD video and do other CPU intensive processes compared to the Core i7 which was designed more for a desktop machine.

      Tho it helps if the CPU is designed to handle it.

      Yes, but emulation of x86 in the CPU level (or technologies made to make emulation easier) might run afoul of Intel's agreements with AMD

      --
      Taxation is legalized theft, no more, no less.
    52. Re:if they do that by Dogtanian · · Score: 4, Insightful

      Aside from the problems mentioned here, there's also the other issue that as soon as they exposed/permitted the native core instructions to be used, people would use them and they'd have to support them forever .

      (Disclaimer: I don't know that much about chip design, and some bits of the next paragraph may be misleading, half-remembered or misrepresent Intel's motives.)

      IIRC, during the x86's long development (or mutation), Intel added some features because they could, and because it seemed like a good idea at the time. Some of those features were never much used, or turned out to be not such a good idea, or were rendered mostly irrelevant by design changes in the next generation. Still, once they'd been included they had to support them for evermore, because they couldn't risk breaking compatibility with code that *did* use them.

      Now, I assume that the current chips' RISC cores was designed because it suits Intel's current way of implementing the x86-emulation/execution (and as the other guy said, wasn't designed for end-user/program use). If Intel come up with a smart, new and totally different design/architecture, the way things stand, they could simply replace it with a different core that used different microcode instructions, and change the x86 "wrapper".

      If Intel had exposed the microcode of the previous generation, they'd either have to stick with the old core architecture, or include it as emulation. Except because it was emulated, it probably wouldn't run as fast, and old (i.e. *existing*) programs that used the old microcode would probably run slower on the new chips. So they'd be forced to stick with the old architecture.

      (Essentially it's the hybrid software/hardware equivalent of (e.g.) someone exposing the implementation details of a Java class simply because they "can" or "someone might want to use it". If in future they want to redesign that class in a more efficient manner, they have to worry about code that used the old implementation's internal workings.)

      All because they exposed some microcode functionality which wasn't even meant to be anything more than a "black box" implementation detail- unsuitable for general use- in the first place.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    53. Re:if they do that by athlon02 · · Score: 3, Funny

      Just don't upset the ALPHA overload and you should be fine. Otherwise, he met send you on a one way trip on the Itanic.

    54. Re:if they do that by et764 · · Score: 3, Informative

      Not all virtualization requires hardware extensions. In fact, VMware was doing it long before Intel and AMD added virtualization support to their processors. VMware pulled this off by doing dynamic translation, where the virtual machine monitor would transparently rewrite native x86 into virtualized x86 code. For the most part this was just doing a straight copy, and perhaps rewriting some jump addresses. Privileged code that runs in the OS kernel had to be rewritten as something equivalent that would run fine in an unprivileged process.

      This really isn't so different from running .NET or Java code. The code starts out compiled to a virtual instruction set, and the JIT compiler translates this on the fly to something that can run natively on the CPU.

      This is also how Rosetta worked in Mac OS X to run PPC apps on an x86 processor. XBox 360 does a similar thing to run old XBox games, since the 360 uses a PPC processor but the old XBox was x86.

      Sure, you take a performance hit in doing this, but the apps generally get rewritten to run natively eventually, and the ones that don't end up being old enough that they run faster on modern hardware even with the extra translation layer.

    55. Re:if they do that by tgd · · Score: 2, Informative

      Or someone who never owned an Alpha system.

      Strictly speaking you COULD run x86 apps on them, but the performance was abysmal.

    56. Re:if they do that by dkh2 · · Score: 4, Informative

      I'd like to see a chip that can run in a x86 'translated' mode and a 'native' RISC mode, much like was done with 32bit/64 bit.

      Already ready to use. The Transmeta Crusoe processor does this on the fly. Of course, now they're owned (or is that pwned?) by Novafora so your guess is as good as mine whether this will survive.

      --
      My office has been taken over by iPod people.
    57. Re:if they do that by beav007 · · Score: 3, Funny

      RTFA carefully.

      You must be new here...

    58. Re:if they do that by maxume · · Score: 2, Informative

      You inverted Microsoft and Intel (Microsoft is the $140 billion company).

      Intel basically drives investment in fab technology, I wouldn't harsh on them too much.

      --
      Nerd rage is the funniest rage.
    59. Re:if they do that by tobiasly · · Score: 2, Funny

      Either way, holding AMD in violation of their agreement means they would effectively forfeit 64-bit licensing rights as well, and that makes no sense for them.

      Says you! That Itanium line is going to just take off any day now, and then AMD and their crazy backwards-compatible technology will be left out in the cold!

    60. Re:if they do that by Anonymous Coward · · Score: 2, Insightful

      I think you missed something here. The revocation of the 64 bit licenses would mean that intel would not be able to sell any of their current CPU's (except for maybe some models of the atom). There isn't some magic "remove infringing IP" from all of our designs wand. A stalemate at this point would be disastrous for both companies. This is nothing more than intel grandstanding. It will be settled privately long before it ever reaches a courtroom.

    61. Re:if they do that by earthforce_1 · · Score: 2, Insightful

      Linux users would be less screwed since everything is open source - same apps, just new binaries to work with your old data. Windows users would be screwed royally since they would almost certainly have to relicense/repurchase all their apps, or run their old ones in emulation. But apple got away with it...

      --
      My rights don't need management.
    62. Re:if they do that by petermgreen · · Score: 2, Informative

      emulation works to a point but

      1: it's very hard to get it perfect
      2: you generally lose a lot of performance. This is not an issue when emulating really old stuff but trying to emulate x86 on the comparitively slow arm is going to give terrible performance.

      Sometimes you can get away with it. Apple did a pretty good job all considered. Sony screwed up pretty badly imo (even thier PSone emulation has bugs and thier partially software PS2 bc on the european PS3 was pretty terrible at least with ratchet and clank, the american PS3 with bc had pretty much all the PS2 hardware inside sidesteping the emulation problem). I haven't tried the XBOX 360 myself so I can't comment on that.

      I doubt some small netbook vendor would have the resources to do this well even if there were suitable (as in faster than the intel chips they are trying to replace) CPUs on the market.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    63. Re:if they do that by Hal_Porter · · Score: 2, Informative

      Consoles are a special case though. They are sold at a loss and subsidised by the cost of the games.

      Usually when a new generation console is introduced they have back compatibility by essentially including bits of the old console - i.e. the first PS3s, or by some hokey emulation code - the XBox360. The PS3 dropped the legacy hardware to cut prices and become profitable. The XBox360 could only play 13% of XBox games, which is actually quite an achievment considering how real time consoles are and that the CPU and GPU were totally different.

      So manufacturers talk about back compatibility as a marketing bullet point. It's not really true though. I don't think it matters - people that care about old games will have the old console anyway and they can play them on that.

      PCs are different to this - people have loads of software which they absolutely want to use when they buy a new machine. And compatibility break will cripple sales of a new OS.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    64. Re:if they do that by Hal_Porter · · Score: 3, Interesting

      That's not true. Windows NT has run on Mips, i860, Alpha, PPC and Itanium. None of them ever had even 1% of the market.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    65. Re:if they do that by bonch · · Score: 2, Informative

      Except that they didn't lose backwards compatibility. Do you even know about Universal Binaries, Rosetta, or OpenStep's legacy of hardware (and even operating system) independence?

    66. Re:if they do that by marcosdumay · · Score: 2, Insightful

      "...the majority of the world is still running 32bit OS..."

      Yeah, but Intel would lose the entire server market.

    67. Re:if they do that by kasperd · · Score: 2, Informative

      Translation and register renaming take up tiny amounts of die compared to the instruction cache savings of x86.

      Only L1 cache actually make a distinction between instruction cache and data cache. And AFAIK the instruction cache actually stores the translated instructions, so there isn't going to be any savings from x86 code being more dense. But maybe you meant that the space you save for x86 instructions stored in L2 and L3 cache are worth more than the overhead of translation.

      --

      Do you care about the security of your wireless mouse?
  2. MAD by Anonymous Coward · · Score: 2, Insightful

    At stake is not only AMD's ability to build processors that use Intel's x86 technology, but also Intel's ability to use AMD's x86-64 tech in its CPUs.

    So, surely this is a case of mutually assured destruction for both isn't?

    1. Re:MAD by DragonWriter · · Score: 3, Interesting

      So, surely this is a case of mutually assured destruction for both isn't?

      Something like that, but not perfectly symmetrically. While x86_64 is well-enough established that it would be inconvenient for Intel to have to go back to x86 and build a new, non-derivative extension with similar capabilities, it would be less of a problem for them than AMD losing the rights to use x86-anything.

      Given that Intel and AMD don't have serious competition for desktop PCs right now, its possible that the a result that hurts Intel a lot but AMD more in the short term could benefit Intel in the long term, though really the intent here is almost certainly to get concessions from AMD on the basis that Intel may be able to prevail in court, and AMD stands to lose more if the agreement is terminated; it is extremely unlikely that Intel's goal is to terminate the agreement.

    2. Re:MAD by powerlord · · Score: 3, Insightful

      Something like that, but not perfectly symmetrically. While x86_64 is well-enough established that it would be inconvenient for Intel to have to go back to x86 and build a new, non-derivative extension with similar capabilities, it would be less of a problem for them than AMD losing the rights to use x86-anything.

      Like heck.

      It would force both AMD and Intel to pull their chips temporarily.

      The only thing Intel could sell is the Atom (32 bit only), and the original version of the Core (again, 32 bit only).

      Yeah ... they'd still have a product to sell on the market, but a staggering amount of their products (most of the Core line) would simply stop.

      Likewise AMD would still have the Geode and other chips to sell, but their desktop/server line would have to stop.

      MS would probably continue okay (I hear Win7 runs okay on the Atom and old Core processors), but it would mean that we'd be back at 32bit limits for things like memory.

      The groups that would be hurt the most (beyond AMD and Intel)? Computer retailers like Dell and Apple (whose products would have to be redesigned), and the American computer economy as a whole (I'm sure you'll be able to find AMD and Intel chips made in China that would keep shuffling off the assembly line just fine).

      --
      This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
  3. Well this should be fun to watch by Anonymous Coward · · Score: 2, Interesting

    This has been brewing for years. AMD with it's anti-competitive lawsuit against Intel, and now this. AMD's suit is mostly won, but Intels new suit could really make things interesting.

    AMD's next line of Phenom II are coming out soon and AMD doing better in terms of sales. Intels feeling the pinch from Netbook sales pulling out the rug from the I7's anticipated sales. The market is changing and it favors AMD in the terms that people are spending less. Intel has a lot more to loose then AMD and that's why this is going to be so good.

    If Intel wins the consumer will lose, if AMD holds its ground Intel will suffer a large drop in sales and the giant of the company will fall. Any sort of drop in sales from Intel and it will have to make major cutbacks and Intel will loose all sorts of momentum just to save it's cash. The middle ground is what we all will hope for but even that could really hurt the Intel giant.

  4. and the answer is... by je+ne+sais+quoi · · Score: 2, Insightful

    And the answer is... powerPC! But only if someone takes an interest in working on the chip to lower power consumption and heat output. My dual G5 runs great but the sucker sounds like a jet engine taking off when it starts doing something computationally intensive.

    --
    Gentlemen! You can't fight in here, this is the war room!
    1. Re:and the answer is... by the+linux+geek · · Score: 2, Interesting

      I recently acquired a PowerStation made by FixStar, the same people who make Yellow Dog Linux. Since Apple and IBM gave up on Power-based workstations, this is among the last you can get, and it's quite nifty, and fairly reasonably priced ($1250 for quad PPC, 2GB RAM). If you have $6000 extra to throw at it there's also a Cell expansion board. My only real issue with it is lack of compatible 3d graphics hardware.

  5. Business as usual by AKAImBatman · · Score: 5, Insightful

    Intel and AMD like to squabble about licensing every few years. Probably in an attempt to broker a deal that is even more favorable than the last. They usually spend some time posturing in court, bare their claws a little, then settle with a new cross-licensing agreement. If Intel gets too pushy, the feds start staring at them REALLY hard. Which tends to make Intel fall in line.

    Strictly speaking, Intel's argument is pointless. Yes, their deal is with AMD. But AMD's foundry only manufactures the chips, it does not design them. (Unless I somehow misunderstood their fabless plan.) Since the fab creates the chips on behalf of AMD, the licensing is not violated.

    That's my 2 cents worth, anyway. I'm not a lawyer, but I doubt one would make many more comments without viewing the legalese between the two companies.

    1. Re:Business as usual by Chris+Burke · · Score: 3, Insightful

      Strictly speaking, Intel's argument is pointless. Yes, their deal is with AMD. But AMD's foundry only manufactures the chips, it does not design them. (Unless I somehow misunderstood their fabless plan.) Since the fab creates the chips on behalf of AMD, the licensing is not violated.

      It may not be that easy. The Intel/AMD license agreement, for all its notoriety, is completely confidential and thus nobody knows exactly what is in it except for a small number of people at both companies. Despite that, it has long been suspected that part of the agreement is that AMD would not manufacture more than a certain % of its chips at a 3rd party fab, which FoundryCo -- wait, it's GlobalFoundries now, slightly less stupid name -- would almost certainly count as once fully spun off.

      Strictly speaking, though, nobody outside the upper echelons knows. The only thing I'm 100% certain of is that AMD thought about the cross-licensing agreement when they came up with the idea for spinning off the fabs, and would not have done it if they thought it would cost them their license. But of course companies can differ in their self-serving legal reasoning, and who knows maybe they knew they were taking a chance and felt that the global anti-trust inquiries and the threat of losing AMD64 licensing would keep Intel playing ball?

      --

      The enemies of Democracy are
    2. Re:Business as usual by 0xABADC0DA · · Score: 3, Insightful

      If Intel gets too pushy, the feds start staring at them REALLY hard. Which tends to make Intel fall in line.

      One remedy used in the past for monopolies is to take it's patents and trade secrets and place them in the public domain. Even if Intel were to win a complete victory, they could end up losing it all.

  6. Fuzzy on x86 IP by MSTCrow5429 · · Score: 4, Interesting

    Maybe I'm missing something, but how can the x86 architecture itself be subject to copyright? Isn't the protected property not the publicly documented instruction set, but the implementation thereof?

    --
    Slashdot: Playing Favorites Since 1997
    1. Re:Fuzzy on x86 IP by gEvil+(beta) · · Score: 5, Informative

      Maybe I'm missing something, but how can the x86 architecture itself be subject to copyright? Isn't the protected property not the publicly documented instruction set, but the implementation thereof?

      I believe it's not the core x86 instructions, but rather all the various MMX and SSE extensions that have been tacked on in the past 10-15 years. And as mentioned in the summary, AMD's x64 extensions are at stake, too.

      --
      This guy's the limit!
    2. Re:Fuzzy on x86 IP by idontgno · · Score: 2, Interesting

      Not copyright. Patents..

      In other words, Intel claims patents over much of the technology that makes an x86 an x86, and AMD agreed (back in 2001--the patent cross-licensing agreement that's in dispute in this issue). AMD could hardly walk away from the agreement now* and continue to manufacture x86-descended CPUs--their previous acceptance of the patents would be evidence against them in Intel's inevitable patent infringement suit.

      No, I Am Not A Lawyer. And I'm sure it's nuanced much more finely than this. But that's kinda the Sesame Street version of how this is shaping up.

      Patents.

      * Yes, I know, AMD isn't disclaiming the license agreement; they're saying the new Globalfoundaries fab has rights to those licenses because it's an AMD subsidiary; Intel's saying they aren't and therefore don't inherit the licenses. If it becomes a full-out patent lawsuit nuclear exchange, AMD might be in a position of manufacturing x86s without license, which would be bad, or not manufacturing x86s at all, which would be worse, or not allowing Globalfoundaries to manufacture x86s, which would be stupid.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    3. Re:Fuzzy on x86 IP by forkazoo · · Score: 2, Interesting

      Maybe I'm missing something, but how can the x86 architecture itself be subject to copyright? Isn't the protected property not the publicly documented instruction set, but the implementation thereof?

      My understanding is that if you wanted to make a 286 clone designed from scratch, you would probably be in the clear. OTOH, if you want modern extensions like MMX, or even SSE/AMD64, then you need a license for the more modern variations. That said, the whole field is deeply complicated and unclear. Some parts of the situation have never really been tested in court so anybody claiming to have a 100% understanding of the legal issues is almost certainly mistaken.

  7. More... by Jaysyn · · Score: 3, Insightful

    ... stupid intellectual property bullshit.

    --
    There is a war going on for your mind.
  8. What's really at stake by davidwr · · Score: 3, Insightful

    At stake is not only AMD's ability to build processors that use Intel's x86 technology, but also Intel's ability to use AMD's x86-64 tech in its CPUs."

    At stake is money and corporate posturing.

    This is just another day of corporate King Of The Hill.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  9. Intel will license it by truthsearch · · Score: 5, Insightful

    Intel will definitely work this out. They're almost forced to license x86 to prevent being labeled a monopoly. Many believe the only reason they licensed it in the first place was to prevent legal action by the justice department. With a competitor making similar chips it's hard to claim they strong-arm computer manufacturers into using their products.

    1. Re:Intel will license it by hemp · · Score: 2, Interesting

      The real reason for the licensing had nothing to do with the Judicial system.

      In order to bid on certain government/DOD contracts you are required to have a second source for most items. This to prevent all of the usual issues you normally get when dealing with a single source, namely they go out of business and you can't find them any more.

      By allowing AMD to license and manufacture, Intel was able to bid on more government contracts. This all occurred back in the 80's prior to Intel dominating the CPU field.

      --
      Skip ------ See the latest from http://www.anArchyFortWorth.com
    2. Re:Intel will license it by eggz128 · · Score: 5, Interesting

      Intel licensed x86 to AMD originally because Intel was unable to keep up with demand.

      It wasn't so much that Intel couldn't keep up with demand, more that IBM's policy required that a second source be available just in case they couldn't.

      AMD has now breached the license. Intel has no responsibility to keep AMD in business. Intel can get another foundry to make x86 CPUs. There's no law against being a monopoly.

      No, there is no law against being a monopoly. There are laws against being an abusive monopoly however. Intel has been convicted of abusing it's monopoly status in Japan, has at least been accused of doing so in the EU. Maybe AMD could file a complaint in the USA also and have it successfully investigated. Once convicted of being an abusive monopoly the rules change.

      Natural law is against being a failure like AMD.

      In theory the UK monarch can veto any law parliament puts before him or her. In practice, vetoing rarely happens as it can lead to the removal of the monarchs head. Intel should be careful just how far they push this as states could just decide they are abusing their position and remove their right to x86 all together.

    3. Re:Intel will license it by blair1q · · Score: 3, Informative

      Intel wasn't actually convicted of abusing its monopoly status. It wasn't a monopoly. And it wasn't convicted.

      It settled with an economic commission (none of these things are courts) and at that point decided it was cheaper to pay the fine (less than $50 million; about an hour's pay to Intel) than to fight it in a court.

      In the settlement Intel admits no wrongdoing, and the Japanese assert none.

    4. Re:Intel will license it by Dun+Malg · · Score: 3, Informative

      You are apparently ignorant of history.

      You apparently can't even be bothered to read the wikipedia entry on AMD.

      Intel licensed x86 to AMD originally because Intel was unable to keep up with demand.

      AMD was a second source for the 8086 and 8088 because IBM demanded two sources, not because Intel couldn't make enough.

      AMD refused to stop making x86's, and sued Intel to keep the right to do so. AMD actually LOST that case,

      AMD was the one who challenged the x86 license cancellation and won the case in arbitration, and after numerous appeals it was upheld b the California Supreme Court.

      They renewed the license in 2001. AMD has now breached the license.

      Given that the licensing agreement isn't public, your analysis is clearly pulled straight from your rectum.

      Intel has no responsibility to keep AMD in business.

      The amusing thing about cross licensing agreements is that they cross. You can't really cancel half a contract. If Intel forces AMD out of the x86 CPU market... then Intel is out of it too, unless they intend to use something other than EMT64, which is a licensed implementation of AMD's proprietary AMD64.

      Natural law is against being a failure like AMD.

      Oh, I see. Your an Intel fanboy. That explains it.

      who moderated this fool up so high?

      --
      If a job's not worth doing, it's not worth doing right.
  10. Old and busted = Mhz by QuantumRiff · · Score: 4, Interesting

    New hotness = Lawyers on retainer!

    I for one, will miss the Megahertz Myth race.. But hey, it might go crazy when AMD has a GPU as the Vector CPU in the computer, and Intel has to sell a 63-bit processor.

    I guess it will be exciting to watch new developments again.. Seems they've gotten a little to comfortable with each others positions lately..

    --

    What are we going to do tonight Brain?
  11. Poor Microsoft by zigfreed · · Score: 3, Interesting

    Long live StrongSparcPC_x64! Poor Microsoft, how on earth would they sell Windows 7?

    1. Re:Poor Microsoft by nonicknameavailable · · Score: 3, Insightful

      with FUD

      --
      Mendacem Memorem Esse Oportet
    2. Re:Poor Microsoft by Forty+Two+Tenfold · · Score: 3, Funny

      Wif fud? Liek a Win7 license in a Happy Meal? I think MacDonald would rather keep the Apple pie license.

      --
      Upward mobility is a slippery slope - the higher you climb the more you show your ass.
  12. It won't succeed by girlintraining · · Score: 2, Insightful

    If Intel becomes the exclusive provider of x86 chips, they'll be smacked by the government with anti-trust litigation (Note: I did not say WHICH government, my fellow silly Americans). It was the same with Apple being the company Microsoft pointed to when it was hit with anti-trust. Intel is simply hoping that AMD is too fearful to engage in litigation, or risk folding the business, simply to expose Intel to government action -- they are betting that AMD simply accepts whatever monthly tribute is required by Intel, thus assuring it's continued irrelevance without being wholly dismissed out of the market. If AMD still had its balls, they'd call the bluff and tell Intel to go to hell -- because Intel needs AMD a lot more than they're letting on.

    --
    #fuckbeta #iamslashdot #dicemustdie
  13. GF may not be a "subsidiary" according to Intel by mr_mischief · · Score: 2, Interesting

    ...but isn't that generally what a company that is in majority controlled by another company called?

    Also, would AMD really have been so short-sighted as to sign a cross-licensing agreement with Intel that wouldn't allow AMD to contract an unlicensed third party to fabricate AMD's designs under AMD's licenses as an agent of AMD?

  14. x86 was a hack anyway by nurb432 · · Score: 3, Interesting

    Not trying to sound like a troll here, but x86 should have been retired decades ago. It designed in a totally different era and was never intended to scale well and its been a series of hacks to get it to do so. ( it was impossible to predict where we were going back then, the cpu industry was far too immature )

    Sure, they have done wonders keeping it moving, but its long since time to start over with a clean architecture.

    My preference would be MIPS or SPARC inspired, but thats just me, either way its time to move on/up.

    --
    ---- Booth was a patriot ----
    1. Re:x86 was a hack anyway by cdrguru · · Score: 2, Interesting

      Problem is, you would lose 50-70% of the existing computer market. Apple tried switching CPUs and in both cases needed massive hand-holding of customers, emulation and dedicated support from vendors. Sorry, but the Windows market doesn't have the same level of vendor committment.

      Sure, lots of major software vendors (think Symantec) would help out their customers and would have a new chip architecture supported from day 1. And if there were no other vendors out there, it would be a pain-free transiation. The problem is for Windows that people are running software that was created in 1990. And the vendor may not exist any longer. Microsoft has seen recently how much fun it is to tell these people they have to find a different solution because the world has moved on. It didn't go well.

      It would not go well changing hardware architectures, either. What we have is an investment in the billions of dollars in the x86 instruction set. While the source might be somewhat portable (ha!), the object code in user hands is not. Emulation and virtualization could help some, but it isn't the final answer and would not help everyone out. Just as it wasn't the solution for Apple either time.

  15. At one level by mutantSushi · · Score: 2, Interesting

    At one level, wouldn't it have been a smarter, lower-litigation-cost approach if AMD had spun off their NON-FOUNDRY (design) operations but kept all the x86 rights under the same house as the foundry? (if the design company wants to make x86 parts with other foundries, as they have done previously if I'm correct, they simply designate it as "design contracting" FOR the Foundry Company which holds the x86 rights (profit stream going to AMD, but that's a contract detail irrelevant to x86 licence).

    At another level, what IF Intel ends AMD's x86 licence?
    Isn't the point of the licence in the first place that AMD also has their own signifigant patents they could sue Intel for violating? I just don't see the logic in this, especially given that Intel seems to be doing GREAT compared to AMD, and AMD's continued existence gives Intel an anti-monopoly defense as long as they continue to compete in the x86 market.

    At another level, this certainly seems big enough an issue to bring up the legitimacy of patent monopolies with regards to anti-trust law. US law doesn't generally hold (business) monopolies to be illegal per se, but I believe EU law *DOES*, and if Intel would gain a mainstream CPU monopoly by kicking AMD out of the x86 business, there would be repurcussions. If there was no x86 competition (VIA of course "exists"), the chances of EU nullifying x86 patents (or establishing "open" standardized licencing ala MP3) would seem to rise dramatically, which seems counter to Intel's interests.

  16. Maybe Intel is scared of globalfoundaries? by foxalopex · · Score: 3, Interesting

    Hmm, I wonder if the reason for this is Intel is scared of Globalfoundaries? If I'm not mistaken, the folks who bought the foundry from AMD are the same folks who are building in Dubai. You know the place where money flows like water and they're willing to waste billions to build custom islands? If that's the case, it is possible that AMD could be ramping up their production and process dramatically which would negate any gains Intel has. AMD also seems to have a more market friendly history with other companies than Intel has. Perhaps this is Intel's attempt to gain a monopoly before their ship sinks?

    1. Re:Maybe Intel is scared of globalfoundaries? by TinheadNed · · Score: 4, Insightful

      The tiny problem with Dubai is its money isn't made in oil, but in banking and tourism. One good indicator of how fucked its economy is, is that they're passing a law banning journalistic discussion of the economy.

      And all the new building projects are being shelved as well.

      http://www.kippreport.com/kipp/2009/01/21/what-freedom-of-speech/

    2. Re:Maybe Intel is scared of globalfoundaries? by Xtravar · · Score: 2, Insightful

      Dubai is sinking like a rock lately. Overpriced real estate, overpriced living, with nothing of substance behind it.

      http://smashingtelly.com/2009/02/15/bye-bye-dubai/

      --
      Buckle your ROFL belt, we're in for some LOLs.
  17. Stupid. by Shads · · Score: 2, Interesting

    I personally think that's a damn stupid threat for Intel to make. AMD is arguably the only company that is preventing Intel from being broken up as a monopoly... you don't threaten to bury your only competition when you're nearly a monopoly. The various governments around the world aren't appreciative of that type of behavior. Unless they would like to be broken into dozens of pieces.

    --
    Shadus
  18. Dont see why they need a licence by Eravnrekaree · · Score: 2, Insightful

    First of all, AMDs foundry probably is considered to have inherited the licence so I dont know if Intels claims really hold up.

    Its been a long time since the chip architecture and schematic of AMDs chips have been directly based on Intels, if they ever have been. The only thing they share is the instruction set. Instruction sets are basically a language or communication protocol and these should not be copyrightable, just as someone could not copyright HTML, IM protocols or English. Only an implementation of software of these can be copyrighted not the language itself.

    In my opinion, AMD does not need any licence to implement the ISA in the first place, just as a licence is not required to implement an SQL server or a computer language. Languages are simply not copywritable.

    1. Re:Dont see why they need a licence by Fulcrum+of+Evil · · Score: 2, Interesting

      So, by "get steamrolled" I have to assume you mean, license their new patent or whatever allowed them to outcompete you and then get back in the game thereby causing a more rapid improvement?

      No, I mean use their massive power of scale to incorporate your innovation (which is licensed at some unknown price set by persons unknown), improve their brand while yours is nonexistent, and figure out how to make the product without paying you fees, all in less time than it takes you to reocup R&D. Or they could steal your idea anyway, but that happens already.

      Oh, wait...you meant you fear competition and hope to profit for life off of one halfway decent idea?

      Patents are protection from competition for a period of time in exchange for documenting your work. Taking that away hardly makes it appealing.

      It's hard to tell what you really mean.

      And you seem to have overlooked follow on effects in favor of feel good sentiments.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    2. Re:Dont see why they need a licence by TheRaven64 · · Score: 2, Informative
      When people talk about patents on instructions, what they really mean is patents on the only sensible way of implementing certain instructions. This was the case, for example, in MIPS Technology's patent on unaligned load and store instructions in a RISC processor. There were ways around this, but they are slow and complicated. People implementing MIPS cores had three options:
      1. License the patents from MIPS Technology.
      2. Create a core which didn't implement these instructions.
      3. Come up with some unrelated way of implementing them.

      The patent (U.S. Patent No. 4,814,976) covered a specific way of implementing four instructions. If you implemented them in a different way, then you would not be infringing, but I don't know of any companies that did this (by the way, the patent expires this year, so expect to see more complete MIPS implementations start appearing). A few licensed the patents. Most implemented almost-MIPS architectures, where the four relevant instructions were omitted. GCC and a number of other compilers have switches that allow you to generate code which doesn't use these instructions and an operating system can (very slowly) catch the illegal instruction exception and emulate them for legacy code.

      --
      I am TheRaven on Soylent News
  19. Bait and swtich by olddotter · · Score: 5, Interesting

    This is probably just high stakes gambling. AMD has little to lose. (I say that as an AMD share holder looking at my $2.49 stock price.) Intel has more to lose if they have to redo the 64Bit code. According to the reading, if Intel wins, they get rid of AMD, and become a defacto monopoly having to face US and EU anti-trust regulators. If AMD wins, they get to go along as before and Intel can't sell 64-bit CPUs that people want.

    Basically I bet AMD's lawyers are saying "Go ahead make my day." Given the above even if Intel wins in court, they lose.

  20. Lead, follow, or get the hell out of my way. by geekmux · · Score: 2, Informative

    But the big draw of windows is the inertia of 1,000,000 one-off apps that businesses have written. Microsoft would be scared of people moving to another architecture just because if people were making a (painful) switch anyway, they might look at the alternatives.

    If you wrote the damn app, then learn to recompile it and move on to whatever/whomever is going to be pimping procs next month or next year. If you're that worried about your legacy apps, then learn to use virtualization.

    Moores law didn't get to be a "law" by playing nice and waiting around. Lead, follow, or get the hell out of my way.

    Inertia is as fast and powerful as the people behind it. Adapt or die. It's that simple.

  21. Bring back Alpha... by argent · · Score: 2, Interesting

    If I recall correctly, both Intel and AMD have licensed Alpha technology from DEC-I-mean-Compaq-I-mean-HP. Maybe they could get together with a 64-bit architecture that actually works well.

  22. Re:"open" patent licencing as remedy to monopoly by tinkerghost · · Score: 4, Informative

    Monopolies *ARE* illegal

    No, their not. Abusing a monopoly position is.

    I can certainly patent sexwidget and have a perfectly legal monopoly as the only company in the world producing them. Only if I try to force people to do other things not directly related to my sexwidget in order to get access to them is it considered abusing my monopoly status. In other words, if I try to force retailers to purchase other products like sexfoo & sexbar as a requirement for being able to sell sexwidgets, I'm abusing my monopoly.

  23. No. by AcidPenguin9873 · · Score: 5, Insightful

    I wish Slashdotters would stop with the incessant "x86 sucks" mantra. You're all fools.

    There's plenty of crufty old instructions in the x86 ISA; no modern compilers generate them though, so no one cares that they're there. They take up a couple pages in the ISA manual I guess. The die area it takes to implement them is totally, completely insignificant. They're either in microcode (along with a bunch of other really useful instructions) or the hardware already exists for some other reason.

    There's plenty of crufty segmentation and weird ways of laying out memory and whatnot; no modern OS uses that though, so no one cares that it's there. And again with the ISA manuals and some transistors. And there's plenty of modern paging and flat memory models and whatnot too.

    AMD and Intel both know how to make good, fast, and (relatively) small hardware to decode variable-length x86 instructions. Yes, of course an x86 decoder is bigger (i.e. more expensive, more difficult to implement, etc.) than a RISC fixed-length decoder, but again, no one cares because we already know how to do it fast enough and cheap enough. Check out an x86 die photo sometime; most of it is cache. Probably about 1/50th is decoder.

    And CISC-style+variable-length instructions get you a smaller code footprint and thus better instruction cache utilization vs. what you'd get with a fixed-length instruction stream. Examples: common ops get shorter instructions, there are more flexible addressing modes, more flexible sources/dests within a single instruction, you get one x86 instruction (no more than 15 bytes) to do what would take multiple RISC-style instructions (probably more than 15 bytes).

    Sure there's the crufty x87 floating point stack. But there's also the shiny new SSE/SSE2/SSE3/whatever instructions, and modern compilers can exclusively use SSE/SSE2 to do the exact same thing (-mfpmath=sse does it in gcc). And again, die area for x87 FP stuff isn't a big deal since a lot of the hardware is shared with SSE.

    ISA extensions have been added to cover all the newfangled SIMD stuff and virtualization you can want. AMD64 covers 64-bit stuff. And 64-bit stuff gives you extra registers too (8 extra integer, 8 extra SSE for a total of 16 each), which is great and a nod to the large number of registers that RISC machines give you.

    In short, what the hell is everyone bitching about?

    1. Re:No. by Anonymous Coward · · Score: 2, Interesting

      AMD and Intel both know how to make good, fast, and (relatively) small hardware to decode variable-length x86 instructions. Yes, of course an x86 decoder is bigger (i.e. more expensive, more difficult to implement, etc.) than a RISC fixed-length decoder, but again, no one cares because we already know how to do it fast enough and cheap enough. Check out an x86 die photo sometime; most of it is cache. Probably about 1/50th is decoder.

      If this were all true, how is it that the ARM Cortex-A9 chip is able to get four superscalar RISC cores on a 65nm chip running at over 1GHz ... yet using only about 1 watt of power? Intel's single-core Nano may run at a faster clock, but it uses maybe twice the power and it can't compete with a quad core superscalar RISC CPU.

    2. Re:No. by Wrath0fb0b · · Score: 2, Interesting

      If this were all true, how is it that the ARM Cortex-A9 chip is able to get four superscalar RISC cores on a 65nm chip running at over 1GHz

      And how many actual instruction does that retire per second? Does its FPU perform at even a fraction of the equivalent x86 (I was surprised to see that it even had one -- I wrote a small program for my ARMv4 phone and spent a solid hour wondering why a program that runs in a few seconds on my desktop took many minutes on there. Punchline: don't do double-precision floating point math on your phone)? What about pagetables, interrupts, DMA and coherent cache? Memory controller? FSB/QPI?

      ARM is a wonderful architecture for my mobile phone but it's never going to be enough for actual work. Maybe a netbook running a stripper version of 'nix, but I'd have to see it first to believe it.

    3. Re:No. by TheRaven64 · · Score: 2, Interesting

      Considering that Acorn were running a multitasking graphical operating system on 25MHz ARM chips, I think you might need revisit your definition of 'real work'. You should also take a closer look at the interrupt architecture of ARM if that's one of the things you believe is superior on x86.

      The Cortex A9 scales to four cores on a single die and runs at over 1GHz, while keeping a power envelope of under 1W. If you've only used ARMv4 then you're probably unfamiliar with the NEON instruction set included in most recent ARM chips. This provides 128-bit vector support and both integer and floating-point instructions. The Cortex A8 comes with NEON as standard (it's an optional extension on other ARM7 architecture cores). If you're really doing anything FPU-intensive, however, you should take a look at the on-die DSP that comes on most Cortex A8 chips, such as the OMAP3 or i.MX5 lines.

      A modern ARM chips is faster in every respect than the CPU in the old ThinkPad that I still use for real work. It's not as fast as a Core i7 or a POWER6 by any means, but in terms of performance per watt - which translates directly to battery life - it does very well.

      --
      I am TheRaven on Soylent News
  24. Oh well, X86 was nice while it lasted by Orion+Blastar · · Score: 2, Interesting

    Looks like we either choose ARM or PowerPC to replace X86 technology and run X86 programs via emulation.

    --
    Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  25. Have you ever used an Itanium box? by PipingSnail · · Score: 2, Informative

    Have you ever used an Itanium box?

    Jeez, what an awful piece of cr*p. Sound of a vaccum cleaner, performance slower than an equivalent x86, Mhz for Mhz (timeframe: 2000/1). Well maybe no in benchmarks, but if you had a box, side by side, both running Whistler, you couldn't tell the difference.

    I had an early pre-release Intel box (well, I had several) plus pre-release Visual Studio and compilers. I ported a 2,000,000 line C++ CAD app from 32 bit MFC to 64 bit MFC. We did the port, but the box did not sing. It was horrible.

    5 years earlier I'd used Sun's Windows emulation environment running Windows apps on Sparcstation pizza boxes. That was better.

    Itanium is much more of a dead platform than x86.

    I don't know how expandable SPARC is, in terms of future bandwidth, but if its available its a reasonable legacy bet, given Sun have the emulator software.

    Real shame they dropped Alpha. That was a good platform. Ahread of its time. We had one in our office early nineties, running Digital UX. Sometime in 90-94. That thing was fast, compared to the competition.

    ARM would be excellent though, I'd love that to happen. Same platform for desktop, mobile, embedded, low power, high performance. All we need is multi-core (sorry, haven't followed it closely enough to know if that is the horizon).

    I've only used 2 machines in my life that have sounded like vaccuum cleaners:
    1) Motorola Exorciser, 6809 development system with 8" floppies
    2) Intel development Itanium box (several of).

    Both were [polite]not very good[/polite].

  26. Re:Hi there, anyone remember VIA? by BUL2294 · · Score: 2, Interesting

    The NEC V20 was an 8088 replacement, but it really was an 80186 processor with an 8088 pin-out. The V30 was the 8086 version. Having come to market some 8 years after the 8088/8086, they incorporated design improvements and new instructions, but were generally about 30% faster. They were great for spreadsheets but sucked with games--games of that era utilized published timings for instructions. "Turbo" XTs didn't affect them too much since every instruction that took x amount of time on a 4.77MHz 8088 took x/2 time on a 9.54MHz 8088. On a V20/V30, games would seem to speed up or slow down based on what instruction was run...

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
  27. Re:Hi there, anyone remember VIA? by irieken · · Score: 2, Insightful

    Yes, VIA is still around, and they make some decent little 64-bit x86 processors that sell under the name Nano.

    The Nano processor actually does a pretty good job of holding its own against the Atom; edging ahead in almost every area, except for power consumption.

  28. Laugh now by symbolset · · Score: 4, Interesting

    The ARM netbooks and embedded devices are coming and there's nothing Microsoft or Intel can do about it except adapt and compete. The time when you could defeat a good technology with an evangelist is long gone since the public now knows evangelists are just shills for hire. The day a MS rep could derail a Linux deployment with a sneer has passed. Sorry Enderle, your day is done.

    Intel will choose to compete and they have a good start because they started years ago. As the Atom die shrinks and gains SOC capabilities, its power requirements will come down. Maybe not to ARM levels, but to an acceptable level faster than ARM can bring their performance up to acceptable levels for a good user experience. Microsoft will choose to use the tools they have, and fail to adapt. That's what they do. They can't grasp a market that's abandoned the need for them. It's alien to their corporate culture. After they've failed in the market they'll buy an ARM OS vendor and try, but that's five years hence. and they'll buy five of them badly and integrate them poorly and we'll laugh at their ineptitude here.

    Ultimately Intel will win this one but there will be some interesting side stories and products between now and then. Microsoft will lose because they choose not to port to the interesting new platform Linux runs on already, and so when the channels merge again they will have lost share. By then low power devices might be most of the share, at least for end user devices.

    --
    Help stamp out iliturcy.
  29. You don't know how this works by symbolset · · Score: 4, Interesting

    Intel can shut down AMD's ability to use the X86 technology without giving up the AMD-64 technology if they can show that AMD defaulted on the agreement.

    AMD can use the X86 technology and prevent Intel from using the AMD-64 technology if they prevail.

    A court is going to have to measure this. The smart money is on a settlement but barring that Intel will win.

    Let us meet here again in seven years, when the matter is settled.

    --
    Help stamp out iliturcy.