Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: dougSF30 who wrote (163294)	6/30/2005 2:44:08 PM
From: kpf	Respond to of 275872

doug You bet if it was that easy AMD would have been happy to package K8 in every possible way Rich wants it, for whatever socket or bga-layout. K.

To: dougSF30 who wrote (163294)	6/30/2005 2:52:21 PM
From: Rink	Read Replies (1) \| Respond to of 275872

Doug, I side with Klaus on this one. Horus just connects to Opteron via HTc. I don't expect HTc to change much with socket F except maybe for higher speed (1.2/1.4GHz are possible with HT v2.0), and will at least be backwards compatible (because the 1GHz HT Opteron chips can be for as far as I recall be inserted in 800MHz HT Opteron boards too). So Horus is not likely to care that much what socket Opteron is in. EDIT: I'm not entirely sure about my hypothesis though. I'm sure socket F when introduced will make use of HT v2.0, I'm not sure though about if it will use 16b HTc busses (like currently), or 32b HTc busses that are also specified by that HT v2.0 spec. That would explain the additional pins for socket F (1207 iirc). Regards, Rink