Aaron Durbin 8c20399a42 haswell: wait 10ms after INIT IPI ... There should be a fixed 10ms wait after sending an INIT IPI. The previous implementation was just waiting up to 10ms for the IPI to complete the send. That is not correct. The 10ms is unconditional according to the documentation. No ill effects were observed with the previous behavior, but it's important to follow the documentation. Change-Id: Ib31d49ac74808f6eb512310e9f54a8f4abc3bfd7 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/2780 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>		2013-03-19 05:26:12 +01:00
..
amd	GPLv2 notice: Unify all files to just use one space in »MA 02110-1301«	2013-03-01 10:16:08 +01:00
armltd	ARMV7: minor tweaks to inter-stage calling and payload handling.	2013-02-20 20:49:16 +01:00
intel	haswell: wait 10ms after INIT IPI	2013-03-19 05:26:12 +01:00
samsung	exynos5250: add RAM resource beginning at physical address	2013-03-14 00:04:13 +01:00
via	GPLv2 notice: Unify all files to just use one space in »MA 02110-1301«	2013-03-01 10:16:08 +01:00
x86	SMM: link against libgcc	2013-03-18 20:51:26 +01:00
Kconfig	Fix microcode selection code	2013-02-27 21:01:53 +01:00
Makefile.inc	Fix microcode selection code	2013-02-27 21:01:53 +01:00