Peter Stuge wrote: >> but how to turn on intel processors AND via C3 processors ? >> > > This is the first time it has been done. > Supporting several CPUs on one socket is not so new though. > The code does not really support more than one CPU "type" at a time. > Not exactly. All required infrastructure is there and we have been doing that many, many times. For example for Core Duo and Core 2 Duo CPUs. The difference here is that the two CPU types come from different vendor directories, but that shouldn't be an issue.
Check the cpu_table[] array of each supported CPU and arch/i386/lib/cpu.c:cpu_initialize()/set_cpu_ops() to learn about the matching. > It would be nice to improve this because the AM2 mainboards can use > both k8 and fam10, but it's not being worked on. > The problem with K8 and Fam10 is not a CPU issue but a northbridge issue. All CPU specific code can be executed just fine, but in our model the northbridge is always fixed part of the board and not of the CPU, which is why it is somewhat hard coded. This is not a problem for stage2, but only for auto.c. Basically auto.c needs to do know both/several northbridges and choose which one to use. Stefan -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
