I had the same thought. To me it makes more sense to do that. But I think AMD wants to wait and see how the new Core Duo's perform in the desktop arena. My thinking is they'll only give Athlon 64's, X2's, etc 400mhz FSB's if they have to.
:?: I dont get it :?:
FSB and AMD CPUs. Huh ? No FSB there any more since the K8... There is a Hypertransport reference @200 Mhz, most people are referring falsely to as "FSB". But if you mean that, why raise it to 400 ?? The Hypertransport speed is already at 1000 MHz ... I dont see any performance increases, if you raise the reference freq, and lower the multiplier to get HT1000.
Furthermore to that HT333 topic ... I personally never believed that. Go to hypertransport.org and check the whitepapers, specifications etc. The reference freq. is 200 Mhz. Every hypertransport device has to support that frequency. Anything else in *incompatible*.
Thus, a HT333 would be incompatible, too. Of course AMD can do that, most overclockers do, but why should AMD overclock itself ? To get that fancy "1:1" divider for DDR2-667 speeds ? Nope, first there is no 1:1 divider at all, as the memory freq. is derived with a divider from the CPU clock. Second, if you would do it, what would happen if you wanna use DDR2-800 modules ??
Easiest way for AMD to do it, is like DDR333 is achieved nowadays.
In conclusion, it is obvious, that everything else than a 200
Mhz reference freq. is not needed, and totally nonsense.
When I first heard that HT333 rumours, I though about that these might necessary for testing DDR2-667, because early engineering CPUs might not have the new, needed mem dividers, yet. Now, after I read that "nice" test @DDR2-400 speeds here, I am even more convinced.
At Xtremesystem.org somebody with access to AM2 chips also states, that due to the reported performance bug, memory is running only at DDR2-400 speeds. So all in all it is still not 100% sure, as I do not know how reliable is that Xtremesystem source. But I am convinced 90%, that the given numbers at THG are DDR2-400 ones.
byebye
FalseInformation