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 : Rambus (RMBS) - Eagle or Penguin -- Ignore unavailable to you. Want to Upgrade?

To: Bilow who wrote (59196)	10/30/2000 9:23:23 AM
From: John Walliker	Read Replies (1) \| Respond to of 93625

Carl, That means the motherboard makers will be making boards with as many as 9 RIMM slots. That's really good news - thanks for letting us know - until you told me that I thought one could not get machines with more than eight RIMM slots. euro.dell.com But maybe I forgot about the extra Rambus channel that Intel have introduced for graphics memory - that would make it nine slots altogether:-) John

To: Bilow who wrote (59196)	10/30/2000 9:44:00 AM
From: Ali Chen	Read Replies (1) \| Respond to of 93625

Carl, what could be possible interpretation of the following data: images.anandtech.com ??? I also am very sorry for the intersymbol interference. I must be falsely assuming that 400 MHz of rambus is smaller than 133 MHz of DDR, and it is DDR which crosses multiple clock boundaries, and not Rambus:) BTW, it is all fault of Intel who broke the original and nice Rambus proposal of 1990, which was: 1. stack all 32 chips like a sandwich (to solve the overheat problem, you could put a sliced heat sink between the chips, like in double cheese-burger, or just stop all chips and never access them); 2. multiplex all address and data, you could save extra few wires and save lots of money; 3. eliminate all turn-around cycles - if you are so precise and the speed of light does not bother you, who needs them! 4. Branch those sigle-ram-burgers like a tree with multiple auxiliary controllers instead of lineing RIMMs up. The whole protocol must be so fast, so who would care about extra latency across those controllers; This is all fault of all these guys who actually try to manufacture something - it must be so boring and ineffective compared to diarrhoea of lucrative IP.