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 (163314)	6/30/2005 3:29:27 PM
From: Rink	Read Replies (1) \| Respond to of 275872

Doug, did you read the edited version or the orginal version of my post? Here's the bit I added: 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). 32b HTc would make it incompatible with 16b HTc included in Horus. I'm far from sure though if socket if is for 32b HTc, as I'm not sure at all what all the additional pins will be used for (they're not only for two channel DDR2). As for Horus I really don't know why it's not on the market by now. If socket F continues to use 16b HTc v2.0 I think it's logical that the reason why Horus is not released yet has nothing to do with socket F. Completely clueless I remain, Rink