Slashdot Mirror


AMD Cuts X2 Processor Prices

BDPrime writes "AMD is cutting prices for its X2 processors, according to an update on its microprocessor pricing list. The cuts refer to AMD's Athlon 64 FX and Athlon 64 X2 chips. Some of the price cuts are almost in half."

5 of 206 comments (clear)

  1. Re:To tell you the truth... by ZachPruckowski · · Score: 5, Insightful

    There was a summer price cut around the time of the C2D launch. These are timed to deal with the launch of the ultra-low-end C2Ds, and the price-cuts expected as the new Core 2 Quadros push C2D prices down. AMD's got nothing new until Q3's Barcelona, so they're fighting better chips with cheaper chips.

  2. Re:Waiting for the corresponding cut on Core2 Duo by rsmith-mac · · Score: 5, Informative

    The price cut is in a little less than 2 weeks(April 22nd). Shamelessly ripped from AnandTech:

    Intel Core 2 Extreme QX6800    2.93GHz x 2     4MB x 2     $1199
    Intel Core 2 Extreme QX6700    2.66GHz x 2     4MB x 2     $999
    Intel Core 2 Extreme X6800     2.93GHz         4MB         $999
    Intel Core 2 Quad Q6600        2.40GHz x 2     4MB x 2     $530
    Intel Core 2 Duo E6700         2.66GHz         4MB         $316
    Intel Core 2 Duo E6600         2.40GHz         4MB         $224
    Intel Core 2 Duo E6400         2.13GHz         2MB         $183
    Intel Core 2 Duo E6300         1.86GHz         2MB         $163
    Intel Core 2 Duo E4300         1.80GHz         2MB         $113

  3. Re:Is it enough? by tom8658 · · Score: 5, Insightful

    The fact that we're stuck with x86 isn't Intel's fault. At the time, CISC was considered a good idea, and as for endianness.... I won't even go there.

    Intel has tried to move away from x86: look at the Itanium and Itanium II. Intel gambled that they could find enough ILP with their compiler, and lost, but at least they moved off of x86, right?

    The fact is, because x86 was so wildly successful, and because so much software was written for it, Intel had to ensure that future processors were compatible with the x86 instruction set. Doing otherwise would have been deliberately alienating a large part of their market share. It could be argued that x86 compatibility (or lack thereof, more specifically) is one of the major reasons why IA-64 was unsuccessful. Completely moving off of x86 would be devastating to the company, and irresponsible in the eyes of their shareholders/employees.

    I can't believe that any engineer in his right mind would actually want to stick with IA-32 in the face of its glaring defects, they're very bright people, and if you need proof of that, just look at the Core. But if you want to sell consumer chips, you don't have any other choice.

  4. One example doesn't make a rule by jd · · Score: 5, Insightful
    In fact, AMD's HyperTransport specs are available for free to anyone. Intel's PCI/PCI-X/PCI-e specs are only available to paid subscribers. Not exactly open, is it? But, again, one example doesn't make a rule.

    And what of chip companies that do publish specs? There are MANY chips from FreeScale (formerly Motorola's semiconductor division) that include fantastic levels of documentation. All the calls, all the functions, all the features. There are bugger all drivers in any Open Source *nix (xBSD, Linux, Plan9, you name it) for the S1 encryption chip. You want to talk about supporting those vendors who support Open Source? Then support them by adding that support.

    Let us get down to basics, here. Part of the reason why companies like ATI can avoid supporting Open Source is because the Open Source community has, itself, failed to support the Open Source community. We have not been perfect, shining examples of our own standards and have no right to expect others to adhere to ideals we ourselves fall desperately short of.

    Sure, the Open Source community lacks the kind of funding needed for this sort of stuff. So does AMD, whose profits were almost a billion short of expectation, whose net worth is now not much more than ATI prior to being bought, and whose future (due to Intel's near-monopolistic control over the industry and near-inexhaustible supply of funds) is severely in doubt. AMD has less than a tenth of the money of Intel and can't afford the current price-war for much longer. In the meantime, Intel can not only afford it but can afford to make next-gen components that have exactly the same flaws in concept as all their products have always have. Intel can afford it, Intel will essentially kill AMD, and Intel will only correct the flaws in the logic the next time it is threatened by a chip company.

    (I may sound a little harsh on Intel there, but it's basically true of all corporations. Quality for the sake of quality is not a concept most managers comprehend, and "engineering excellence" is an oxymoron in any group outside of a few fringe development projects and maybe a couple of Formula 1 teams.)

    If support for Open Source were a criteria, I'd say support nobody and move to another planet. As the old NASA joke goes, there is intelligent life on Earth but it's only visiting. There isn't any meaningful support for Open Source, outside of a handful of individuals.

    What about IBM? All those 500+ patents they freed up! Yeah, and how many projects do you see based on them? None? Is that a surprise, when most were hardware patents? Outside of OpenCores, I really don't see many people being able to do much with pipeline optimization or CPU scheduling, and frankly most coders there working on CPUs have been doing just fine using their own methods of solving these problems, and anyone likely to want a high-end 64-bit Open Source chip would probably be looking at the Open Sourced UltraSparc. IBM have released lots of bits of project in the past, but never really maintained them and never really did anything with them. You been using IBM's GUI-based Apache management tool? Ever realized IBM had one?

    The community should, by rights, support anything and anyone it can, AMD included, because a monoculture would be far far worse than the putrid stench we have at the moment. The existing mess can be fixed, with a lot of time and a lot of patience. Monocultures are stagnant cultures are cultures waiting to die. What we have right now is no great shakes, but I'll take it over a living death any day. The dead can't be cured - well, unless they're a kipper.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  5. Re:all the benchmarks are 32-bit by oojah · · Score: 5, Informative

    Where's your proof?

    You've already had someone respond with a link to benchmarks showing exactly the opposite of what you claim:

    http://www.pcstats.com/articleview.cfm?articleid=2 097&page=12

    Where are the benchmarks that show what you claim?

    Cheers,

    Roger

    --
    Do you have any better hostages?