diff options
| author | Angel Pons <th3fanbus@gmail.com> | 2021-12-18 22:25:07 +0100 |
|---|---|---|
| committer | Felix Held <felix-coreboot@felixheld.de> | 2022-02-24 01:18:56 +0000 |
| commit | fa5ed059eb6fef1aa1681fbc7b38052b2028c1ac (patch) | |
| tree | 6dc67b2015e4f45b3cf842bda771d23ffd0c0848 /src/northbridge/intel/ironlake/raminit.c | |
| parent | e2531ffaa87be5c26005ff986db8492a03f809e3 (diff) | |
| download | coreboot-fa5ed059eb6fef1aa1681fbc7b38052b2028c1ac.tar.gz coreboot-fa5ed059eb6fef1aa1681fbc7b38052b2028c1ac.tar.bz2 coreboot-fa5ed059eb6fef1aa1681fbc7b38052b2028c1ac.zip | |
nb/intel/ironlake: Fix some quickpath init magic
Correct some Quickpath initialisation steps according to findings from
two different Intel reference code binaries as well as MCHBAR register
dump comparisons between vendor firmware and coreboot.
The MSR_TURBO_POWER_CURRENT_LIMIT information comes from EDK2 sources.
Tested on Apple iMac 10,1 (Clarkdale, aka desktop Ironlake), QPI init
now completes successfully instead of causing hangs before raminit.
Also tested on HP ProBook 6550b (Arrandale, aka mobile Ironlake), still
reaches payload (e.g. TianoCore).
Change-Id: Icd0139aa588dc8d948c03132b5c86866d90f3231
Signed-off-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/60216
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
Diffstat (limited to 'src/northbridge/intel/ironlake/raminit.c')
| -rw-r--r-- | src/northbridge/intel/ironlake/raminit.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/northbridge/intel/ironlake/raminit.c b/src/northbridge/intel/ironlake/raminit.c index 55c10b7e0b41..fe67f0d0a3e9 100644 --- a/src/northbridge/intel/ironlake/raminit.c +++ b/src/northbridge/intel/ironlake/raminit.c @@ -2937,7 +2937,6 @@ void raminit(const int s3resume, const u8 *spd_addrmap) info.last_500_command[0] = 0; info.last_500_command[1] = 0; - info.fsb_frequency = 135 * 2; info.board_lane_delay[0] = 0x14; info.board_lane_delay[1] = 0x07; info.board_lane_delay[2] = 0x07; |