/openbmc/u-boot/arch/x86/cpu/broadwell/ |
H A D | cpu.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/cpu/x86_64/ |
H A D | cpu.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/cpu/qemu/ |
H A D | qemu.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/lib/fsp/ |
H A D | fsp_common.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/cpu/ivybridge/ |
H A D | cpu.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/cpu/quark/ |
H A D | quark.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/arch/x86/cpu/coreboot/ |
H A D | coreboot.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
/openbmc/u-boot/common/ |
H A D | board_f.c | diff 76d1d02fd280ef7ad63a97c3a80bd765bf5596fa Tue Mar 28 11:27:30 CDT 2017 Simon Glass <sjg@chromium.org> board_f: x86: Use checkcpu() for CPU init
At present we misuse print_cpuinfo() do so CPU init on x86. This is done because it is the next available call after the console is enabled. But several arches use checkcpu() instead. Despite the horrible name (which we can fix), it seems a better choice.
Adjust the various x86 CPU implementations to move their init code into checkcpu() and use print_cpuinfo() only for printing CPU info.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|