On Tue, 21 Mar 2017 14:19:18 +0000 Sam Kuper sam.kuper@uclmail.net wrote:
Dear all,
Hi,
Nicola Corna pointed out to me that adding a timeout at https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/nehal... might solve this problem.
(I guess the idea is that instead of waiting indefinitely for the ME to load, Coreboot should instead just wait for a defined amount of time and then plough on regardless.)
I am not a C programmer, so am not competent to add that timeout.
Adding the timeout is easy, however I'm not sure how much we should wait. I used one second to be large but I've no idea if it's enough or not.
Please can anyone here provide a suitable patch for me to test, or failing that, point me to a similar timeout in another architecture's raminit that I might use as a starting point?
I'll send one. I didn't check for typos or spelling yet in the commit message.
Denis.
On 27/03/2017, Denis 'GNUtoo' Carikli GNUtoo@no-log.org wrote:
On Tue, 21 Mar 2017 14:19:18 +0000 Sam Kuper sam.kuper@uclmail.net wrote:
Nicola Corna pointed out to me that adding a timeout at https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/nehal... might solve this problem.
(I guess the idea is that instead of waiting indefinitely for the ME to load, Coreboot should instead just wait for a defined amount of time and then plough on regardless.)
Please can anyone here provide a suitable patch for me to test, or failing that, point me to a similar timeout in another architecture's raminit that I might use as a starting point?
I'll send one. I didn't check for typos or spelling yet in the commit message.
Many thanks :)
P.S. For the benefit of future readers, the thread with Denis's new patch for Nehalem/etc can be viewed here: https://www.coreboot.org/pipermail/coreboot/2017-March/083798.html
-
Denis 'GNUtoo' Carikli -
Sam Kuper