To: John Walliker who wrote (32524 ) 10/21/1999 11:24:00 PM From: Bilow Respond to of 93625
Hi John Walliker; About that 1.5x voltage movement... This is highly confusing, but at the moment I think you are right about the 1.5x drive condition, which would be caused by two chips passing off drive without having a delay between them. Assuming perfect chips, with the master clock travelling exactly the speed of the incoming data signals, (which makes the outside chips therefore start driving proportionately earlier than the inside chips.) Lets see if I can paraphrase this, and understand it... If the first chip is outside, then its incoming trailing edge will pass through the second chip at the time that the second chip starts to drive. Therefore the second chip will see only reflections from the first chip, and no 1.5x voltages get driven. But if the first chip is inside, then the second chip would have to drive through both the (outward) reflected and the outward direct signals from the first chip. This is because the second chip has to start driving before the first chip ceases, it being farther out. This means that the second chip would have to drive the bus to 1.5x a logic 1. The above makes sense to me. I agree that some sort of state machine could keep those signals apart, but I got the impression (possibly in error) that such a state machine is not present in the standard RDRAM interface, as described on the Rambus web site. The reason I got that impression was because I noticed a table which gave the latency versus the various possible configurations. I don't recall the table including the added cycle that a miss would require. Eventually, I'll take another look at it. Their design would be much simpler if they simply increased the output compliance of the RDRAMs enough to drive a 1.5x signal. I very difficult design. When I mentioned to my engineering buddy that it seemed that Rambus was passing off reads between different chips, without dead time on the bus, he started laughing. He does more stuff outside chips than I do, so we may be misreading (or not reading) something in the spec books. It would be a lot easier to understand if they had doubly terminated that bus. I guess they didn't for at least three reasons. One was the increased power consumption, (I believe my calculations assumed a doubly terminated data bus, it is likely that my current drive calculations were in error...) The second reason was the increased number of passives required. The third was the fact that the doubly terminating some busses, but not others, would result in a system where some pins had to drive twice as much current as others. That would make it quite a bit harder to match the propagation delays. (Output pins of the controller, in particular.) New rumor of 820 not being launched Monday from Reuters. -- Carl