See attached patch.
Marc
Marc Jones wrote:
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Looks good.
Acked-by: Peter Stuge peter@stuge.se
If some enterprising person wants to try to apply this to v3 that would help.
I know there are people out there looking for ways to help, and this is one of them. I can verify the patch.
We are getting closer to having k8 support ready in v3, such that new platforms can go into v3 first.
thanks
ron
Peter Stuge wrote:
Marc Jones wrote:
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Looks good.
Acked-by: Peter Stuge peter@stuge.se
Thanks Peter, I was going to repost this with some changes. I think that there is a corner case I didn't correctly account for. :)
Marc
Marc Jones wrote:
Peter Stuge wrote:
Marc Jones wrote:
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Looks good.
Acked-by: Peter Stuge peter@stuge.se
Thanks Peter, I was going to repost this with some changes. I think that there is a corner case I didn't correctly account for. :)
Resubmitting this patch. I think I worked out all the corner cases and made it a little easier to understand.
Thanks, Marc
On Wed, Oct 01, 2008 at 02:57:03PM -0600, Marc Jones wrote:
Resubmitting this patch. I think I worked out all the corner cases and made it a little easier to understand.
This will probably break the build on some boards, e.g.:
Processing mainboard/asus/a8v-e_se (i386: ok) Creating config file... ok Creating builddir...ok Compiling image on 1 cpu .. FAILED after 4s! Log excerpt: cache_as_ram_auto.c:(.rom.text+0x3a34): undefined reference to `printk_debug' collect2: ld returned 1 exit status make[1]: *** [coreboot] Error 1
I think the reason is this:
- printk_debug("Current fid_cur: %x\n", fid_cur);
- printk_debug("Requested fid_new: %x\n", fid_new);
All other printk_*'s in this file are "protected" similar to this:
#if K8_SET_FIDVID_DEBUG == 1 #if CONFIG_USE_PRINTK_IN_CAR printk_debug("%s%x\r\n", str, val); #else print_debug(str); print_debug_hex32(val); print_debug("\r\n"); #endif #endif
I'll check if that'd fix the issue.
Uwe.
Uwe Hermann wrote:
On Wed, Oct 01, 2008 at 02:57:03PM -0600, Marc Jones wrote:
Resubmitting this patch. I think I worked out all the corner cases and made it a little easier to understand.
This will probably break the build on some boards, e.g.:
Processing mainboard/asus/a8v-e_se (i386: ok) Creating config file... ok Creating builddir...ok Compiling image on 1 cpu .. FAILED after 4s! Log excerpt: cache_as_ram_auto.c:(.rom.text+0x3a34): undefined reference to `printk_debug' collect2: ld returned 1 exit status make[1]: *** [coreboot] Error 1
I think the reason is this:
- printk_debug("Current fid_cur: %x\n", fid_cur);
- printk_debug("Requested fid_new: %x\n", fid_new);
All other printk_*'s in this file are "protected" similar to this:
#if K8_SET_FIDVID_DEBUG == 1 #if CONFIG_USE_PRINTK_IN_CAR printk_debug("%s%x\r\n", str, val); #else print_debug(str); print_debug_hex32(val); print_debug("\r\n"); #endif #endif
I fixed several platforms that didn't have prink_* support for a different fix. I would rather fix the platforms since K8 always has CAR. The print_* PRINTK_IN_CAR is really ugly and would like it to go away....
I will run abuild and see what platforms need some printk love.
Marc
On Wed, Oct 01, 2008 at 02:57:03PM -0600, Marc Jones wrote:
Marc Jones wrote:
Peter Stuge wrote:
Marc Jones wrote:
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Looks good.
Acked-by: Peter Stuge peter@stuge.se
Thanks Peter, I was going to repost this with some changes. I think that there is a corner case I didn't correctly account for. :)
Resubmitting this patch. I think I worked out all the corner cases and made it a little easier to understand.
I've tested the patch on my MSI K9N Neo (MS-7260) but I'm not sure if the changes I've seen in the logs are correct.
It seems the CPU frequency changed from 1.8 to 1.0 MHz. See attached logs/diffs for more information.
Uwe.
Uwe Hermann wrote:
I've tested the patch on my MSI K9N Neo (MS-7260) but I'm not sure if the changes I've seen in the logs are correct.
It seems the CPU frequency changed from 1.8 to 1.0 MHz. See attached logs/diffs for more information.
That is bad. Can you set K8_SET_FIDVID_DEBUG and send the new minicom?
Thanks, Marc
On Tue, Oct 21, 2008 at 05:54:57PM -0600, Marc Jones wrote:
Uwe Hermann wrote:
I've tested the patch on my MSI K9N Neo (MS-7260) but I'm not sure if the changes I've seen in the logs are correct.
It seems the CPU frequency changed from 1.8 to 1.0 MHz. See attached logs/diffs for more information.
That is bad. Can you set K8_SET_FIDVID_DEBUG and send the new minicom?
Yep, see attachments.
Uwe.
Uwe Hermann wrote:
I've tested the patch on my MSI K9N Neo (MS-7260) but I'm not sure if the changes I've seen in the logs are correct.
It seems the CPU frequency changed from 1.8 to 1.0 MHz. See attached logs/diffs for more information.
Uwe, What is the make and model # of your CPU? Thanks, Marc
On Tue, Oct 28, 2008 at 04:43:23PM -0600, Marc Jones wrote:
Uwe Hermann wrote:
I've tested the patch on my MSI K9N Neo (MS-7260) but I'm not sure if the changes I've seen in the logs are correct.
It seems the CPU frequency changed from 1.8 to 1.0 MHz. See attached logs/diffs for more information.
Uwe, What is the make and model # of your CPU?
$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ stepping : 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps bogomips : 2012.03 clflush size : 64
processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ stepping : 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps bogomips : 2012.03 clflush size : 64
(from vendor BIOS, with cpufreq scaled to 1GHh, usually 1.8GHz)
Uwe.
Uwe, Thanks for all the help! Sorry this took so long.
I found the issue (and a few others along the way). This updated patch should work now. It should also get you another 100MHz with your cpu :)
Marc
On Wed, Oct 29, 2008 at 06:00:39PM -0600, Marc Jones wrote:
Uwe, Thanks for all the help! Sorry this took so long.
I found the issue (and a few others along the way). This updated patch should work now. It should also get you another 100MHz with your cpu :)
Indeed, thanks! I'm at 1.9 GHz now.
$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ stepping : 1 cpu MHz : 1900.042 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefeh bogomips : 3803.48 clflush size : 64 power management: ts fid vid ttp tm stc 100mhzsteps
processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ stepping : 1 cpu MHz : 1900.042 cache size : 512 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefeh bogomips : 3800.22 clflush size : 64 power management: ts fid vid ttp tm stc 100mhzsteps
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Acked-by: Uwe Hermann uwe@hermann-uwe.de
Please port this to v3 also if possible.
Uwe.
Uwe Hermann wrote:
On Wed, Oct 29, 2008 at 06:00:39PM -0600, Marc Jones wrote:
Uwe, Thanks for all the help! Sorry this took so long.
I found the issue (and a few others along the way). This updated patch should work now. It should also get you another 100MHz with your cpu :)
Indeed, thanks! I'm at 1.9 GHz now.
...
Update K8 FID/VID setup. Add support for 100MHz FIDs (revG).
Signed-off-by: Marc Jones marc.jones@amd.com
Acked-by: Uwe Hermann uwe@hermann-uwe.de
Please port this to v3 also if possible.
Thanks for testing this multiple times. I'll follow up with a v3 patch later today.
r3726
Marc