Unless Barton is surprisingly better than Tbred, AMD can only sit back and put everything behind Hammer. Course, that's pretty much what they're planning on annyway. Hammer has to be a success or else AMD is screwed, but Hammer is looking good so far.
i have a feeling that amd will make a comeback, when they first came up with the athlon, they tore intel a new one, intel is back on top again, but it probly wont last. it will keep going up and down for years until one up and quits.
how do you shoot the devil in the back? what happens if you miss? -verbal
PIII Tualatin:
- 0.13 die shrink (including 0.13 class gates)
- extra L2 cache
- excelent data pre-fetch (pass-me-down from P4 design)
Athlon Tbred:
- 0.13 die shrink (but already had 0.13 class gates which is why it clocked so high with the 0.18 core)
- same L2 cache
- same data pre-fetch
Barton:
- 0.13 die
- extra L2 cache
- same data pre-fetch
But when AMD 'tore Intel a new one', Intel had been asleep behind the wheel. They were gouging the customer for every last MHz on an incredibly slow upgrade path, and they had very little interest in R & D because to develop something significantly new just wasn't needed in their opinion.
Now, AMD has put Intel on guard. Intel's R & D is churning and burning on new upgrades. (At least in theory.) So anything that AMD does is highly unlikely to catch Intel even half as badly as they did in the past. Simply, Intel is no longer sleeping.
Tech support said take a screen shot.
Putting it down with my .22 was the humane thing to do.
As we all know the latest P4 whips the Athlon due to the much higher clock speed.
Is the barton & T-Bred too little too late for the athlon? Or does the athlon core need a complete overhaul to enter the 0.13 world?
i don't think it is too late for AMD yet. we have to wait the results involving by the improvement of the new 'G' type series TBred as the results of the Barton which is not even coming out yet. thus we can't speculate at once yet.
<i>if you know you don't know, the way could be more easy ...</i>
Now, AMD has put Intel on guard. Intel's R & D is churning and burning on new upgrades. (At least in theory.) So anything that AMD does is highly unlikely to catch Intel even half as badly as they did in the past. Simply, Intel is no longer sleeping.
do you think that AMD is sleeping & its R&D is in vacation even if we are entering in the summer season?
<i>if you know you don't know, the way could be more easy ...</i>
Now, AMD has put Intel on guard. Intel's R & D is churning and burning on new upgrades. (At least in theory.) So anything that AMD does is highly unlikely to catch Intel even half as badly as they did in the past. Simply, Intel is no longer sleeping.
In some respects you are right. HOWEVER, AMD seems to be excelling at leveraging it's partners and partnerships...hypertransport consortium to name one. AMD also seems to be seriously improving it's relationships with chipset developers and motherboard makers. While Intel is seen as the major competition for both of these, AMD is looked at more as a partner.
Finally, Intel certainly has a much greater R&D budget, roughly 7x the size of AMD's. HOWEVER Intel also has to expend far more reseources in all the various subsidiaries it owns.
So yes, Intel can put more resources up against AMD, but AMD has a few extra resources on it's side of the match.
Mark-
<font color=blue>When all else fails, throw your computer out the window!!!</font color=blue>
do you think that AMD is sleeping & its R&D is in vacation even if we are entering in the summer season?
Probably not, but try and imagine seeing and AMD Hammer on a TV commerical *shivers*...I can only imagine how bad that could be, just look at the P4 blue aliends...ick...but, win or lose, live or die, AMD is placing all their guns behind the Hammer, so we can only hope they did their homework and come through for us, the end users.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.