The code: /** * Delay Control Settings table from AMD (MCP 0x4C00000F). */ static const struct delay_controls { u8 dimms; u8 devices; u32 slow_hi; u32 slow_low; u32 fast_hi; u32 fast_low; } delay_control_table[] = { /* DIMMs Devs Slow (<=333MHz) Fast (>334MHz) */ { 1, 4, 0x0837100FF, 0x056960004, 0x0827100FF, 0x056960004 }, { 1, 8, 0x0837100AA, 0x056960004, 0x0827100AA, 0x056960004 }, { 1, 16, 0x0837100AA, 0x056960004, 0x082710055, 0x056960004 }, { 2, 8, 0x0837100A5, 0x056960004, 0x082710000, 0x056960004 }, { 2, 16, 0x0937100A5, 0x056960004, 0x0C27100A5, 0x056960004 }, { 2, 20, 0x0B37100A5, 0x056960004, 0x0B27100A5, 0x056960004 }, { 2, 24, 0x0B37100A5, 0x056960004, 0x0B27100A5, 0x056960004 }, { 2, 32, 0x0B37100A5, 0x056960004, 0x0B2710000, 0x056960004 }, };
/* * Bit 55 (disable SDCLK 1,3,5) should be set if there is a single DIMM * in slot 0, but it should be clear for all 2 DIMM settings and if a * single DIMM is in slot 1. Bits 54:52 should always be set to '111'. * * Settings for single DIMM and no VTT termination (like DB800 platform) * 0xF2F100FF 0x56960004 * ------------------------------------- * ADDR/CTL have 22 ohm series R * DQ/DQM/DQS have 33 ohm series R */
static void set_delay_control(u8 dimm0, u8 dimm1)
There's no support here for a non-terminated bus! Just that one comment.
Also: * Settings for single DIMM and no VTT termination (like DB800 platform) * 0xF2F100FF 0x56960004
Does this mean 1 DIMM, any number of devs? This is not clear.
A change: static void set_delay_control(u8 dimm0, u8 dimm1, int terminated)
terminated is 0 if there is no termination. Then set 4c00000f accordingly?
ron
ron minnich wrote: ...
Yes, see the table in v2. There isn't code in v2 either. I'll work something up next week.
Seems reasonable. Marc
Hello,
Ühel kenal päeval, P, 2008-07-27 kell 22:11, kirjutas ron minnich:
It's correct to do automatic PLL config from bootstraps here, but this is unrelated to the provided log message
So we have it unterminated and it was set up as terminated before or that wasn't an issue for your memtest quest?
What's this? Factory BIOS is GSW? Artec LinuxBIOS-v2 branch should be the reference here instead in that case and if that had it write-through, then it might be wrong, would have to check. Also unrelated to the commit log message as provided
Regards, Mart Raudsepp Artec Design LLC
Thanks for the comments. Mart, the factory BIOS I have sets writethrough. If it should no I will remove this setting. It did not help anyway. I will correct this patch and resubmit.
ron
On 28.07.2008 07:11, ron minnich wrote:
Please mention the conceptually separate dbe62 changes as well or move them to another commit.
Signed-off-by: Ronald G. Minnich rminnich@gmail.com
With the comments below addressed, the patch is: Acked-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Please add "(mainboard dependent)" to the new parameter as well. There's one superfluous space at the end of the line.
Superfluous whitespace after =.
Please make the "mainboard-dependent" remark formatting consistent with the two lines above. Also, there's a superfluous space at the end of the line.
Regards, Carl-Daniel
committed, with all commits taken into account, Committed revision 699.
thanks
ron