Re: [coreboot] [ haswell i7-4600] Why does accessing data in MCHBAR hang the boar?

I keep debugging and find out the MCHBAR+0x5400 - MCHBAR+0x7FFC can be accessed. The address below 0x5400 can cause hang. Zheng From: coreboot on behalf of Zheng Bao Sent: Monday, January 29, 2018 11:03

Re: [coreboot] Power off in Coreboot?

On Mon, Jan 29, 2018 at 1:59 PM, Julius Werner wrote: > In grepping the sources I see the API is provided and only used in a >> handful of cases, mainly x86. >> >> On an ARMv8 target is there a power-off use-case for Coreboot? >> This is strictly from Coreboot perspective,

Re: [coreboot] Power off in Coreboot?

> > In grepping the sources I see the API is provided and only used in a > handful of cases, mainly x86. > > On an ARMv8 target is there a power-off use-case for Coreboot? > This is strictly from Coreboot perspective, not Depthcharge. > You're right, there is no globally standardized power off

[coreboot] Power off in Coreboot?

Folks, We are working through the PMIC requirements for Coreboot on our hardware. I understand the need for Coreboot to command a reboot, e.g. VerStage detects FW_A is bad and wants to try FW_B. What is not clear is what is the use-case for Coreboot to command a power-off. In grepping the

[coreboot] [ haswell i7-4600] Why does accessing data in MCHBAR hang the boar?

After the MRC.bin is loaded and run, the board hang at accessing data in MCHBAR32. If I move MCHBAR32 backward before the MRC.bin runs, it still hangs. It seems has nothing to do with MRC.bin, does it? /* For reference print the System Agent version * after executing the UEFI PEI