Quote Originally Posted by zoson View Post
I've been trying to be nicer and more supportive... But I see a reply like this and I just *have* to chime in that nobody should listen to this. All of the above info is just flat out _bad_ and _wrong_.

RTL values will be different from board to board, chip to chip, and ram to ram. Unless you have the exact same memory kit, board, and chip from the same time period and bins, these values are not translatable from user to user.

Allow the board to set your RTL automatically, write down the values, and then simply tune them manually increment by increment to see if you can actually tighten them down more.

And anything over 1.35v VTT is _DANGEROUS_ for Gulftown processors.
The RTL settings have been known to auto detect too aggressively, you would know this if you browsed i4memory.com. Here is an article on it. There is a formula for RTL and also a link in that thread to an Excel sheet which can be downloaded to guesstimate your RTL. The value you get from the Excel sheet is usually within 1-2. You are correct, each board is different as the traces are longer/shorter going from the processor to the memory but its only going to throw off the RTL by a 1-2 usually and the Excel sheet as a parameter where you can set the latency from processor to RAM (it is defaulted to that of the R3E IIRC).

I apologize about the bad info on the vtt, I don't own a Gulftown. I do know that when my vtt is set to low my gflops are adversely affected on my 3520.